Bringing forth runit integration regarding desktop environments

[Martin Steigerwald]

Martin Steigerwald - 08.02.25, 19:41:31 MEZ:

[… pipewire startup/integration with other inits …]

> 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/pip
> ewire/APKBUILD#L120
> 
> And then it is XDG autostart which should work with all init systems.
[…]
> How to ship this to users is a different question though. Maybe in an
> extra package like "pipewire-xdg" or "pipewire-autostart". And ask the
> maintainer of Pipewire to add a suggests or so. Or in case there are
> additional services for desktops that make sense to be started with
> either XDG autostart or DBUS activation, there could be a more generic
> package like "desktop-services" or something like that. But then how to
> select such a package for users of alternative init systems?
> 
> Another approach would be to make /usr/libexec/pipewire-launcher exit
> immediately when Systemd is found and then ask the Pipeware package
> maintainer to ship both files with the package. That way all users would
> benefit from it. However… not sure whether the Pipewire maintainer will
> accept such an approach. On the other hand I will not know unless I
> ask.

Wait… a… moment…

The desktop file reads:

% cat /etc/xdg/autostart/pipewire.desktop 
[Desktop Entry]
Version=1.0
Name=Pipewire
Comment=Start Pipewire
Exec=/usr/libexec/pipewire-launcher
Terminal=false
Type=Application
X-KDE-autostart-phase=1
X-GNOME-HiddenUnderSystemd=true
X-systemd-skip=true

So shouldn't this just work out of the box whether Systemd is PID 1 or 
not? See both options to skip/hide it under Systemd.

I tend to just make a report to the pipewire package maintainer and see 
where this is going. What do you think?

Best,
-- 
Martin