New issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/20930

Description:
As was agreed when writing the Wayland docs page, elogind is a requirement for a safe wayland session. Therefore, should we make elogind a dependency of the wayland package itself?

Packages like Sway currently have it as a build option, defaulting to a setuid binary instead. Cage, on the other hand, doesn't enable setuid, so it definitely requires elogind (at least in its current state). However, Cage currently doesn't list elogind as a dependency, so if you try to simply install it and run it (without looking at the docs), it will error out due to missing capabilities. Even running as root doesn't work, because then it can't drop privileges properly.

Making elogind a dependency for wayland seems like it would be the best solution for all cases. I would even make a case for an INSTALL message telling the user to enable the service and restart their device (or just log in and out, idk. Whenever I enable elogind I have to reboot for it to work).

Tagging @Duncaen, because you made the case for elogind being a requirement for Wayland.