Summary: | Should /etc/init.d/xdm belong to x11-apps/xdm and not x11-base/xorg-server ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James Gatt <james152> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | alexander, jer |
Priority: | High | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=730644 https://github.com/gentoo/gentoo/pull/16554 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 342661 |
Description
James Gatt
2011-03-01 00:25:06 UTC
Note that you should be able to build x11-base/xorg-server with USE="-xorg -dmx -kdrive" to install none of the server implementations provided by the package. A better place might be x11-apps/xinit Or we should finally let each DM supply their own initscript. We don't have a 'cron' script multiplexing our cron daemons, we don't have 'syslog' multiplexing syslogs... The code needed to start the individual DMs is not so much different between xdm, kdm, gdm etc. Maintaining it in one central place is maybe better. A possibility would be to make xdm/kdm/gdm etc. ship wrapper scripts that set some variables and then call a generic DM starter. (In reply to comment #3) > Or we should finally let each DM supply their own initscript. We don't have a > 'cron' script multiplexing our cron daemons, we don't have 'syslog' > multiplexing syslogs... The idea was that there's no (valuable) use case for wanting to run multiple DMs at the same time. Hence having only one badly-named xdm script. It used to be in xinit a while back and it was moved from there since few DMs and DEs actually use/require xinit tools. Last time we discussed the whole thing, we decided that having the xdm init script installed by xorg-server was the lesser of many Evils™. This can be changed of course, but is it really worth the hassle for all our users and for our documentation? Cheers (In reply to comment #5) > (In reply to comment #3) > > Or we should finally let each DM supply their own initscript. We don't have a > > 'cron' script multiplexing our cron daemons, we don't have 'syslog' > > multiplexing syslogs... > > The idea was that there's no (valuable) use case for wanting to run multiple > DMs at the same time. Hence having only one badly-named xdm script. > > It used to be in xinit a while back and it was moved from there since few DMs > and DEs actually use/require xinit tools. > > Last time we discussed the whole thing, we decided that having the xdm init > script installed by xorg-server was the lesser of many Evils™. > > This can be changed of course, but is it really worth the hassle for all our > users and for our documentation? Yes, if it means anything to not have dependencies that don't really make sense. At the moment some change to the documentation would be required to explain what to do if you want a server that can run desktops and X applications without having to have xorg-server installed on the machine with no monitor that nobody actually sits at. As the examples in comment #3 suggest, the precedent is already there for other services, but if one init file common to all is really a better solution than each DM having its own then the common init file could have its own package and be a dependency of all DMs. Another advantage of that is it would be easier for a DM to fork from that configuration if it became necessary. not really a duplicate but fixed now anyways. see also github PR *** This bug has been marked as a duplicate of bug 730644 *** |