[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: There should not be dependencies on systemd



El sáb, 6 de sep 2014 a las 2:18 , Ansgar Burchardt <ansgar@debian.org> escribió:
Noel Torres <envite@rolamasao.org> writes:
If you need dbus, you should Depend on dbus, and systemd should Provides dbus. Then, if Ann programs her Own Dbus Implementation she can package it as aodi (Ann's Own Dbus Implementation) and have aodi Provides dbus. Same for logind (systemd Provides logind and random-package Depends logind), and any other piece of the big systemd ecosystem. Any dependence on systemd or any other init system should be considered an RC bug (except only packages designed to manage the init system, like an imaginary systemd-tweaking-tool).
That doesn't change anything in practice as long as systemd would be the only package providing logind. So until someone writes an alternative implementation, it would just be useless work.

systemd-shim can get you a logind implementation w/o systemd as PID 1. With the above scenario (virtual packages like logind), apt would be smart and install the least disruptive package. Do you think that would be systemd-shim (no removal of current init) or systemd-sysv (removal of packages)?

Best,
--
Cameron Norman

Reply to: