Bringing forth runit integration, pipewire and user-services

[Lorenzo]

Hi Martin,

On Sat, 08 Feb 2025 19:41:31 +0100
Martin Steigerwald <martin at lichtvoll.de> wrote:

> > 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/pip
> > ewire/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 now did this *exactly* as done in Alpine Linux. Which basically
> means:
> 
> - pipewire.desktop => /etc/xdg/autostart
> - pipewire-launcher.sh => /usr/libexec/pipewire-launcher
> 
> https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/pipewire/APKBUILD#L120
> 
> And then it is XDG autostart which should work with all init systems.
> 
> I will test this over the coming days. But so far it appears to work
> just fine. I removed Pulseaudio package and sound still works :).
> 
> One disadvantage is: Services are not stopped on logout. That is why
> the scripts tries to stop them at the beginning. I am not sure
> whether stopping on logout could be achieved with DBUS activation. I
> doubt it.
> 
> Also of course there is no service supervision. But given the time
> frame for Trixie this might be the most realistic approach.

could you try with the runit-user-session package? It would be very
useful to know if it works with wayland.
https://salsa.debian.org/debian/runit-services/-/tree/user-services?ref_type=heads
Lack of time to test it is currently the main blocker.

Lorenzo