Re: Proposal: Reaffirm our commitment to support portability and multiple implementations
On Sun, 01 Dec 2019 at 22:14:06 +0100, Laurent Bigonville wrote:
> It's bin:libpam-systemd that pulls bin:systemd-sysv (the package that makes
> systemd the init on the system), not bin:systemd. Here it's dbus-user-session
> that pulls it because it needs a logind (dunno if it works with elogind)
> session opened to have the session bus started when the user logs-in.
dbus-user-session needs the `systemd --user` per-uid service manager to be
run whenever a uid has at least one login session, which is functionality
provided by the combination of the systemd service manager (init system)
with systemd-logind. An implementation of the logind interfaces, such
as elogind, is not sufficient. If I remember correctly, libpam-systemd +
systemd-shim was not sufficient either: that configuration provided the
logind interfaces but not `systemd --user`, just like elogind.
The changelog for dbus_1.12.16-2 documents this as the reason why
this dependency was not changed to default-logind | logind when those
virtual packages were added to Policy.
smcv
Reply to: