Is there a reason why there is a hard dependency of systemd? Is it possible to work in elogind? I have only used openrc/elogind based systems and now it is looking like SDDM is getting the final heave and immediately, I am out in the cold.
I understand that sometimes, that’s how the ball bounces but the list is growing:
The Plasma Login Manager should do one thing, log me into the Plasma desktop and you don’t need systemd for that. This is total BS to ice out BSD and systemd free distributions. That is how I feel about it.
I can gladly say that krdp does not require systemd after rechecking
This is likely but might require either work on the elogind side or an alternative on the login manager side.
Essentially there are three ways a process can affect the system state in such a way as to create a new user session.
In the most likely case we are looking at the third option here.
Plasma Login Manager provides UI for the login process and delegates actual session creation to a specialized system service.
This is usually done via a Unix domain socket using some specified protocol, e.g. D-Bus.
The client of the system process does not require any specific implementation of the service, just that it has the capabilities to do what is asked and understands the messages sent to it.
If a capability is present in logind but not yet in elogind (or other alternatives) it can be added there.
If it is present but requires a new message to be sent, then this can also be added to there.
If it is present but requires a different message to be sent, then this can be handled on the UI side as an alternative.
Ultimately any setup will end up making kernel/system calls. If a systemd based setup can do it, so can any other and just needs to expose this in a way that it can be used by the login UI.