This is a refactoring of the xdm init files that are installed by the xorg-server package. A previous attempt to change this was done in https://bugs.gentoo.org/356915 That is really old and is no longer relevant Some reasons for this change into a new package gui-libs/xdm-init - It is a init files only package + a conf.d file for choosing what to run - We are adding support for wayland based display managers using greetd - gtkgreet - tuigreet - agreety (reference implementation) - Running a wayland only environment, we don't need X11 Based on the above it looks better to change this into a new package.
Would we want to use the opportunity and choose a less xdm-ey package name?
(In reply to Andreas Sturmlechner from comment #1) > Would we want to use the opportunity and choose a less xdm-ey package name? Was really tempted to do that. I was afraid this would've been rejected for backwards compatibility reason. But I am all for this. Name suggestions are welcome. I was going to go with gui-libs/greeter-init.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c78bee32adb057ac965b7f60f46980951cfa44bc commit c78bee32adb057ac965b7f60f46980951cfa44bc Author: Aisha Tammy <gentoo@aisha.cc> AuthorDate: 2020-09-10 01:30:09 +0000 Commit: Piotr Karbowski <slashbeast@gentoo.org> CommitDate: 2021-01-30 19:17:42 +0000 gui-libs/display-manager-init: refactor init files out of xorg-server Closes: https://bugs.gentoo.org/730644 Package-Manager: Portage-3.0.5, Repoman-3.0.1 Signed-off-by: Aisha Tammy <gentoo@aisha.cc> Signed-off-by: Piotr Karbowski <slashbeast@gentoo.org> .../display-manager-init-1.0.ebuild | 37 ++++ .../files/display-manager-setup.initd | 13 ++ .../files/display-manager.confd | 13 ++ .../files/display-manager.initd | 234 +++++++++++++++++++++ gui-libs/display-manager-init/files/startDM | 29 +++ gui-libs/display-manager-init/files/xdm.initd | 13 ++ gui-libs/display-manager-init/metadata.xml | 8 + 7 files changed, 347 insertions(+)
*** Bug 356915 has been marked as a duplicate of this bug. ***
