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

Bug#917431: debian-policy: virtual packages: logind, default-logind

On Fri, 28 Dec 2018 at 02:52:09 +0900, Ansgar Burchardt wrote:
> Adam Borowski writes:
> > Thus, the wording would be (as proposed by fsateler):
> >
> > logind: an org.freedesktop.login1 D-Bus API implementation
> >
> > default-logind: should be provided by the distribution's default logind
> > provider (currently pam-systemd)
> So any provider of logind would have to provide the full interface of
> the current interface (including future updates)?

Presumably a package that Provides: logind (= 123) would be expected to
provide the same D-Bus APIs that the logind in systemd 123 did.

Some of logind's APIs are not D-Bus APIs: in addition to D-Bus, it
has an ad-hoc form of IPC using files in /run. I think the files and
their contents themselves are not considered to be public API, but the
functions in libsystemd that read those files are. This is used by other
packages, notably dbus-daemon (which should not normally use D-Bus APIs
itself because that would be a circular dependency) for its deprecated
at_console policy, and policykit-1 for many of its policies.

Are packages that provide logind expected to create the same files in
/run so that libsystemd APIs will work as intended?

> You can start logind without libpam-systemd, it just wouldn't know about
> any session.  So it is about providing hooks to register sessions with
> logind.

A *working* org.freedesktop.login1 implementation, then, perhaps? (If an
implementation of logind doesn't know about login sessions then it can't
really be said to be working correctly.)


Reply to: