Mailinglist Archive: yast-devel (100 mails)

< Previous Next >
Re: [yast-devel] Replacement proposal for the current display-manager.service
On 01/26/2015 11:43 AM, Raymond Wooninck wrote:
Hi Everyone,

The current methodology around starting the Display Manager is a script that
is provided by the XDM package and a single systemd unit file. The script is
doing all kind of stuff it seems, but one of them is reading a sysconfig file
to see which DM should be started.

Most of our Display Managers (SDDM, GDM, Lightdm, etc) already have proper
systemd support and provide their own unit files, but we are removing those in
order to keep the above mentioned methodology working.

My proposal would be to drop the current method (including the script and
special unit files from the xdm package) and to utilize the proper systemd
support from the installed Display Manager itself.

One way (the easiest one) would be that an user can only have a single Display
Manager installed and the are mutually exclusive. The installation and removal
of the unit files can then be done within the DM package itself. The downside
would be that the user can not easily choose which DM to use.

The other way (which would be more comparable to the current method) is that
the Display Managers are providing the proper unit files, but the installation
of them is done through YaST. Like now, through the sysconfig editor, you can
select which Display Manager should be used and this would install the
corresponding unit files.

The changes requires in YaST would be that the user can only select from a
list of Display Managers. Once a DM is selected, YaST should validate if the
corresponding unit file is present. If the unit file is not present, YaST
should offer to install the package. After this YaST should install and enable
the corresponding unit file. This would then generate the correct display-
manager.service which is required by systemd to start the display-manager.

Hi Raymond,

leaving out YaST, what would be the default workflow for user who just installs a single desktop manager?
How should the validation be done? Have will the mapping between the device manager and unit file work?
What happens if I uninstall (just via plain rpm -e) the currently selected DM?

I'm not saying that your proposal is wrong, no way. However, I definitely want to avoid having "if DM is foo, install package bar" in the YaST code and I'd like package operations via rpm or zypper produce expected results.


I would appreciate on-topic replies, feasibility of a proposal and which
proposal would be preferred.



Jiri Srain
Project Manager
SUSE LINUX, s.r.o. e-mail: jsrain@xxxxxxxx
Lihovarska 1060/12 tel: +420 284 084 659
190 00 Praha 9 fax: +420 284 084 001
Czech Republic
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups