On 2018-07-17 12:15, David C. Rankin wrote:
update-alternative has always been a java-selection thing... You have service file for DM, kdm.service, etc.. that provide a straight forward way to set your desktop manager, from there the choice of a window manager is a simple drop down list.
No, we common users in the past only used update alternatives to choose the Java to use, but it has always been for more things, and more things have been added over time. For example, to choose the postgress version.
It seems to me a good idea to use an existing tool designed to choose which one of several alternative possibilities to use. Why use a different method for each choice? Use the same one for all.
You can in the display manager choose the desktop to use from a list, but you can also choose the default one via update alternatives. So, choose the DM and default session in the same tool with a few clicks, instead of searching two config files. Or run two command line commands.
It just seems like an unnecessary move to shoehorn everything people what to switch to an update-alternative scheme, rather than simple allowing control by the designed chooser method. Meaning that when someone looks at configuration in the manual of postres 9.6, etc.. there will be absolutely no mention of anything called Yast2-alternatives, while it may very well address insuring the appropriate service is started.
You are in paranoid mode today :-P
Take a tissana :-)