Quote:
Originally Posted by bassmadrigal
I don't think Eric himself is maintaining elogind. He just uses it to prevent needing systemd. The same thing occurred in Slackware with udev. Since udev was pulled into systemd and no longer separately maintained, to keep up with the development, Slackware switched to eudev, which is udev pulled back out of systemd.
|
Exactly. To be specific, the Wayland compositor part of KWin expects to be able to talk over DBus to a logind implementation. Not necessarily the logind implementation provided by systemd. The logind part of systemd is a rather sane piece of programming and it is not hard to separate that from the systemd sources, and that is exactly what the "elogind" project does, like is also the case for "eudev".
I still have hopes that ConsoleKit2 implements the logind DBus API so that we do not even need elogind in future. But as long as Slackware does not adopt Wayland, there is not even a need for a logind implementation. My "ktown latest" repository does not have Wayland support, therefore it does not have to provide a (e)logind package. My "ktown testing" repository is where I test the addition of elogind in order to make Plasma 5 support Wayland.
The only drawback is that Wayland is required anyway: in order to compile KWin, even for the X.Org support. However, Wayland is not a
runtime dependency for KWin so if you install KWin through a pre-compiled package you would not have to install a Wayland package if you do not want to.
