[opensuse] What is the benefit to using update-alternatives for DM & WM?
Point of interest, After recent discussion, and after reading https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/ 5.2 Use update-alternatives to Set Login Manager and Desktop Session the question of "Why use update-alternatives?" for this configuration functionality instead of "Standardizing around systemd service?" What benefit does a suse-specific 'yast2-alternatives' package have over standardizing with systemd? (nit/note: release notes html format should be tweaked to allow selecting heading lines without "\nReport Bug\n#" getting tagged on) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-17 08:01, David C. Rankin wrote:
Point of interest,
After recent discussion, and after reading https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/
5.2 Use update-alternatives to Set Login Manager and Desktop Session
the question of "Why use update-alternatives?" for this configuration functionality instead of "Standardizing around systemd service?"
What systemd service are you talking about?
What benefit does a suse-specific 'yast2-alternatives' package have over standardizing with systemd?
ditto. This is a user interaction, not a service. What has been done, I guess, is standarize about the upstream method. And as the CLI command to handle update-alternatives (which is not new, has been around for a decade at least) is a bit cumbersome as most CLI commands, well, YaST people added a handy little module to do the choosing. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-07-17 08:01, David C. Rankin wrote:
Point of interest,
After recent discussion, and after reading https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/
5.2 Use update-alternatives to Set Login Manager and Desktop Session
the question of "Why use update-alternatives?" for this configuration functionality instead of "Standardizing around systemd service?"
What systemd service are you talking about?
What benefit does a suse-specific 'yast2-alternatives' package have over standardizing with systemd?
ditto. This is a user interaction, not a service. What has been done, I guess, is standarize about the upstream method. And as the CLI command to handle update-alternatives (which is not new, has been around for a decade at least) is a bit cumbersome as most CLI commands, well, YaST people added a handy little module to do the choosing. 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. 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. Military Intelligence? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
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.
Military Intelligence?
You are in paranoid mode today :-P Take a tissana :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (2)
-
Carlos E. R. -
David C. Rankin