daemon

While it sounds great that it's finally getting some much-needed love, I'm not sure I'm a huge fan of "we need to have everything systemd has". It's good to be opinionated and come up with solutions of your own. Systems work fine without systemd's entire featureset, and it's not openrc's job to be compatible. Out of those you listed, I only think readiness notifications are necessary for the existing OpenRC featureset to work more reliably. I'd rather enshrine a different method of doing user services (for example[1]) instead of having openrc require elogind to take over user session tracking, and I'm not a huge fan of socket activation bloating up the amount of running processes the longer the machine runs, outside of the user's control. [1]: https://github.com/raforg/daemon/

> You mean Slackware users on some random forum. Believe it or not, that's actually the official slackware forum. And whatever solution those guys come up with, it will likely become the official solution. > Besides, the solution they came up with uses XDG autostart which has nothing to do with systemd. The slackware solution involves a project that nobody has heard of before, just so it can imitate the "user-level service" feature provided by systemd: https://github.com/raforg/daemon > Not to mention that it's not even doing the exact same thing as the Gentoo solution and running two more commands in addition to pipewire. The slackware solution requires starting those 3 processes (pipewire, pipewire-media-session, pipewire-pulse) separately from 3 different .desktop files, likely because the daemon tool above can't properly reap the pipe