Quoting Arnt Karlsen ([email protected]): > ..so a good way forward is, treat this policykit/consolekit/logind > etc thing like systemd, pulseaudio etc poetterware.
I'm bemused by people in the Devuan Project wanting to find a compatible substitute for systemd-logind. The entire Debian fiasco was driven by the GNOME maintainers insisting that the 'seat' functionality of ConsoleKit was essential, even though it was an obscure, niche function used by almost nobody. ConsoleKit becoming deprecated meant the GNOME developers needed another 'seat' implementation, which effectively forced choice of systemd-logind with the rest of that marching band. But it should have been, and was, obvious that this trait of reimplementing standard functions badly, EOLing and rewriting codebases frequently, and having ridiculously excessive features and dependencies was far from being confined to systemd but rather affected the entire Freedesktop.org glue suite: udisks2, PolicyKit, ConsoleKit, packagekit, network-manager, etc. Why does PolicyKit want to have itself in charge of all user permissions, including that of the root user? Because the Freedesktop.org coders decided to override user/groups permissions and put themselves in charge via PAM links. And then PolicyKit (policykit-1) requires the rest of the marching band. The only real solution is to do without the Freedesktop.org 'stack' and give GNOME the heave-ho. Devuan appears unwiling to take that step so far, therefore here you are, adopting Gentoo's systemd-logind forked code (which is what elogind is). Debian let itself have its decisions dictated by GNOME. Isn't this making the same mistake, and _even_ in the exact same place in the system architecture? _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
