Hello Julien, > conflicting with systemd is doomed. The replacement of sysvinit with > systemd was careful to keep both init systems co-installable, and I
note that: ① elogind is not part of the init system, only an add-on to enable systemd-like Provides to get some GUI software to run without resorting to using consolekit (which is only available from older versions of Debian) ② systemd currently is the one that isn’t coinstallable (cf. #935304) > think that's something to preserve to avoid providing users with a > loaded footgun with alternative init systems. This is about an alternative logind implementation, which happens to be usable with an “alternative” init system. But what do you propose instead? Also, question back: could elogind work with libsystemd0, and could elogind work with systemd (although while this would address the issue of switching, not Conflicting with systemd increases the chance that elogind is installed by accident, which people also don’t want)? bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg ********** Mit der tarent Academy bieten wir auch Trainings und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an. Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt. **********
