[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 229735] Installing KDE in "/usr/KDE-4.4 breaks Authorization.
From:       Dario Freddi <drf () kde ! org>
Date:       2010-03-08 20:09:19
Message-ID: 20100308200919.ABCEA36A4E () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=229735





--- Comment #5 from Dario Freddi <drf kde org>  2010-03-08 21:09:18 ---
(In reply to comment #4)
> No, I am complaining in the correct place.  From what I have read, KDE has a
> problem with this, therefore, if FD.o won't fix it, someone needs to make a
> patch and post it on the KDE FTP servers.  You don't need a FD.o account to do
> that.

I hope you are joking

> 
> You seem to think that I am just bitching.  This is not the case.  This problem
> is not only a problem for developers, it is a problem for users.  The build
> instructions on TechBase are now useless.  I will have to post a warning that
> if you build KDE-4.4 according to my tutorial it won't work.  That is not just
> an annoyance!  Having a lot of features broken is not just an annoyance, is it?

There is a warning at cmake time. What are the "lot" of features you are
missing? Changing date/time and killing processes running as root? Please. And
you can still move files around.

> 
> I have to say that you are whining.  I have heard this before from developers
> that don't seem to have any sense of personal responsibility as lton as they
> can talk down the problem or blame someone else.  It is KDE that will have its
> reputation further damaged by this problem.  To me, it is simple.  KDE chose to
> use this library.  You say that a user doesn't have to use it, but doesn't that
> mean that things won't work?  Because KDE chose to use this library, it becomes
> KDE's problem and KDE needs to see that it is fixed.

Simple answer: No. So you say that we should have not supported nvidia drivers
in 4.0 or fix drivers ourselves? This is not how this world works, where
everyone has his software and his responsabilities.

> 
> If you hired me

Nice point. IF you hired me.

> to build something for your and there was a problem because I
> used defective materials, what would you think if I told you that it wasn't my
> problem?  And don't use the canard that this is free software so the users
> shouldn't complain.  That doesn't cut it with users.  If KDE is going to make a
> product, they should take responsibility for its quality -- doesn't matter that
> it is free.  It should be a matter of personal pride and personal
> responsibility to see that the KDE team delivers a high quality product.

And do you think you are able to fix defective materials? I wouldn't be so
stupid to tell you to fix something you can't fix yourself, but report the
problem to the manifacturer. Exactly what you are NOT doing.

Or I would tell you to change manifacturer. Guess what, in this case there is
not another one available. So what you do? Live with the problem. It's you
against a full userbase and developer base who understood the issue instead of
coming up with arguments that make no sense at all and accusing KDE of things
which are completely out of our responsibilities, I hope you are realizing
this.

And I'm tired of telling you this because you'll keep refusing this argument.
You have a completely distorted vision of how things work when developing
software, maintainers exist for a reason. And bugs should be reported to them.

P.S.: I'm not the maintainer of polkit and will never be. And I doubt I will
contribute to it as well.
P.P.S.: Can you please file the same bug against any other application using
polkit? I don't like KDE being the only one. NetworkManager, HAL and DeviceKit
are the first on the list. It seems reasonable from what you are saying,
correct?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]