Re: x-session-manager alternative
Eric Gillespie, Jr. wrote:
> > What is a poor sysadmin to do if he wants wmaker to be the
> > default window manager, and yet also wants to have kde
> > (well, konquorer really, but it's all more or less one
> > package) to be installed?
>
> That's a bug in KDE's packaging, IMHO. Konqueror shouldn't depend
> on the KDE session manager, though in fact it does.
>
> But, the alternative can always be put into manual mode and the
> admin can do whatever he likes.
As has been pointed out, I was wrong and konqueror does not depend on
kdebase. So let me restate my question:
What is a poor sysadmin to do when he has 5 users who want kde in all
its glory, and 50 users who want wmaker, and 15 who want other
miscellaneous window managers[1]?
He has to install kdebase. But now he has a x-session-manager
alternative, and X uses that by default. He doesn't want it to be the
default; the sane thing is to make wmaker the default and set up a mere
20 .xsession scripts (or more likely, set up 5 for the kde
users-cum-windows-refugees and let the other 15 fvwm and E diehards fix it
themselves..). Setting up 65 .xsession scripts is far less appealing.
You say the x-session-manager alternative can be put in manual mode, but
it's still going to point somewhere, and X is still going to use what it
points too. All I can think our hypothetical sysadmin could do is make
the alternative point to some hand-cooked script that simply runs
wmaker, but what a gross hack that is to force upon our users..
--
see shy jo
[1] This more or less mirrors usage patters I am seeing amoung linux
users in these parts, but consider the numbers to be hypothetical..
Reply to: