Bringing forth runit integration regarding desktop environments

[Martin Steigerwald]

Hi!

Today I managed to take some time again and go about bringing forth runit
integration. Thankfully Mathias, the maintainer of Incus packages, agreed
to accept a merge request:

#1084990 incus: runit service dir for incus
https://bugs.debian.org

I am now trying my luck with lxcfs as well:

#1087185 lxcfs: runit service dir for lxcfs
https://bugs.debian.org/1087185

I am working with Lorenzo on these. Lorenzo kindly provided me with a very
thorough review about the current Incus service dir I use on my Devuan
Excalibur (based on Debian Testing aka upcoming Debian 13 aka Trixie).


However I wonder about doing some work for desktop integration as well.

I will do a power-profiles-daemon service dir. Probably based on what Void
linux maintainers have been doing and probably still today:

https://github.com/void-linux/void-packages/tree/master/srcpkgs/power-profiles-daemon/files/power-profiles-daemon


And again I also wondered about pipewire integration as well. AFAIR
according to some discussion about it this cannot really be handled as a
system service, but needs to be tied to the user session, probably by
DBUS activation.

Maybe what Alpine does there would be a good approach:

https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/pipewire/pipewire-launcher.sh

I believe I read from a Devuan user that this would work. But I did not
find that mail anymore. So I am not completely sure where to integrate
Pipewire startup properly.


I would like to get both of those work on my laptops first. But once I
have a working approach, I'd look at asking whether maintainers would
accept merge request. Otherwise power-profiles-daemon can go into
runit-services package. I am not sure about Pipewire startup. Maybe it
would need to go into an extra package if the pipewire package maintainers
do not like to see Runit integration in their package.

Of course the unit-translator approach by Mark is also something that
probably can help here, however I prefer hand-crafted service dirs.

Regarding Pipewire as  a session related service an approach that would
work with all init systems would be nice. I bet some kind of DBUS service
activation will work on all init systems.


Regarding Void and Alpine Linux I really wonder about some kind of mailing
list for cross distribution discussion on implementing support for
other than Systemd init systems. At the moment there is a lot of
duplicated effort.

Best,
-- 
Martin