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

List:       kde-commits
Subject:    Re: kdebase/kcontrol/kcontrol
From:       Daniel Molkentin <molkentin () kde ! org>
Date:       2004-12-04 8:36:12
Message-ID: 200412040936.14424.molkentin () kde ! org
[Download RAW message or body]

Am Samstag, 4. Dezember 2004 03:32 schrieb Frans Englich:
> Do not build kcmshell. I'll remove the files later on. I'll also merge
> libkcontrolcommon with kcontrol since it's not needed in kcontrol, unless
> someone objects -- speed improvement.

Why the hell do you want it to go? Did you ever inform core-devel or the 
maintainer about it? Not that I have been particulary active here recently, 
but it would have been nice if you *asked*, plus I had asked several times 
before *not* to change anything in KControl before KDE 4.0 that changes 
something for the user. Mantra: It's bad as it is now, but it's worse to 
change things over and over in every release we do. 

That's no absolute thing, it's good to see people working on it -- if they 
send you an email once in a while before changing vital part of the 
application.

Moreover, as George pointed out, kcmshell is a vital tool. You can't just 
remove it. 

This feels a lot like the guy next door who promises to fix your car, and when 
you return, it's completely tuned - he even did it for free. After asking 
what he changed, he tells you: "Uhm, ob by the way, you can't use your rear 
trunk anymore, it's filled out with an enourmous bass speaker. And now, 
coming back to reality, it's not only my "car", it's everyones car.

I hope you have at least an alternative way to invoke single KControl modules, 
so you can wrap kcmshell with all the parameters it has now. If not, revert 
immediately.

Cheers,
  Daniel
[prev in list] [next in list] [prev in thread] [next in thread]