I would appreciate if you could make it possible to install just the libraries and headers, so that I could test whether my packages build against elogind without actually having to remove systemd.
I'm not sure if this belongs in the tree or not. What about INSTALL_MASK?
INSTALL_MASK would not resolve the blocker. Besides, I don't think I'm the only one who would appreciate being able to test his packages, if your goal is indeed to support elogind Gentoo-wide.
Hmm, how about something as crazy as USE=systemd that builds libraries but connects to systemd's logind? I suppose they use the same API, so it should work.
Sven, do you think this is feasible at all?
(In reply to Andreas Sturmlechner from comment #4) > Sven, do you think this is feasible at all? Libraries and binaries have their own names, the includes are in /usr/include/elogind, and the config is in /etc/elogind. What would clash are: - All man pages but - /usr/share/man/man1/elogind-inhibit.1 - /usr/share/man/man7/elogind.* - /usr/share/man/man8/elogind.8 - /usr/share/man/man8/pam_elogind.8 - /bin/loginctl - /lib/udev/rules.d/* - /usr/bin/busctl - /usr/share/bash-completion/completions/loginctl - /usr/share/dbus-1/system-services/org.freedesktop.login1.service - /usr/share/dbus-1/system.d/org.freedesktop.login1.conf - /usr/share/factory/etc/pam.d/* - /usr/share/polkit-1/actions/org.freedesktop.login1.policy - /usr/share/zsh/site-functions/_loginctl The dbus files are important! They must not be installed, or dbus *will* autostart elogind if systemd-login hasn't registered itself already.
*** Bug 878941 has been marked as a duplicate of this bug. ***
