On Tue, 05 Sep 2000, Simon Hausmann wrote:
> Hi,
>
> I just noticed that a lot of meant-to-be-configurable things in startkde
> are hardcoded.
>
> For example: Do we really need kxmlrpcd on each and every desktop session?
> (at least for example I don't need it on my 64mb-ram laptop)
>
> How about moving it to kdenetwork and starting it via a kcminit module?
> (combined with a kconfig check, so that there is at least a way to
> configure it via kconfig editing (at least ofr 2.0, as a kcontrol option
> would break translations))
>
> IMHO the same applies for khotkeys and kwrited (the latter I like to run
> when I'm at work, but on my single-user-desktop at home I don't need it)

Same applies for klipper. I'm never using it, and don't want to stop it 
manually every time I restart KDE.

Lars

>
> Opinions? Flames? :-)
>
>
> I volunteer to hack three kcminit modules to start those three components
> after a quick kconfig check, and remove their hardcoded entries from
> startkde, if people agree :-)
>
> Bye,
>  Simon