control: tag -1 +pending Hello Simon,
On Sun 30 Dec 2018 at 03:52PM +00, Simon McVittie wrote: > Maybe "via D-Bus and <systemd/sd-login.h>" or "via D-Bus and sd-login(3)"? I've committed the latter. > If a logind provider such as elogind doesn't result in the libsystemd > sd-login APIs working (at least as well as they would with the provided > logind version), would you consider that to be a bug in the provider? > I asked this earlier in the bug and didn't notice an answer (my apologies > if there has been one that I missed). > > I ask because libsystemd users like dbus and policykit-1 cannot be linked > to both libsystemd and libelogind without compiling the daemon twice and > somehow arranging to run the right one for the installed system, which > I think is an undesirable level of complexity; for Debian, we should be > preferring the library that matches our default installation, which is > libsystemd. Derivatives like Devuan that don't have libsystemd at all > are of course free to link their libsystemd users to libelogind instead. We don't seem to have a consensus on this question yet. I don't properly understand the issue, but it doesn't seem like it needs to block adding the virtual packages to the list. -- Sean Whitton
signature.asc
Description: PGP signature
