On Fri, 03 Aug 2018 14:55:11 -0700 Brian Clinkenbeard
<brianclinkenbe...@protonmail.com> wrote:
> [...]
>
> Github description:
> Elogind is the systemd project's "logind", extracted out to be a
> standalone daemon. It integrates with PAM to know the set of users
> that are logged in to a system and whether they are logged in
> graphically, on the console, or remotely. Elogind exposes this
> information via the standard org.freedesktop.login1 D-Bus interface,
> as well as through the file system using systemd's standard
> /run/systemd layout. Elogind also provides "libelogind", which is a
> subset of the facilities offered by "libsystemd". There is a
> "libelogind.pc" pkg-config file as well.
>
> Gentoo description:
> elogind is the systemd project's logind, extracted to a standalone
> package. It's designed for users who prefer a non-systemd init system,
> but still want to use popular software such as KDE/Wayland or GNOME that
> otherwise hard-depends on systemd.
>
> Considering that ConsoleKit is no longer maintained and, according to
> the package changelog, "On Linux, the consolekit package is actively
> harmful and should no longer be installed", elogind is the only
> available seat/user/session management option for Linux users without
> systemd. Most distros that do not use systemd by default (e.g. Gentoo)
> have chosen to use elogind to provide these capabilities.
elogind source tarball is also building a elogind PAM module and a
libelogind library.
IMVHO, the libelogind library shouldn't be package as a public library
and all packages in debian should use libsystemd built from src:systemd
package instead as it would otherwise lead to consistency issues an code
duplication.
Please keep that in mind if somebody is packaging this for debian.
my 2ยข
