Re: OpenRC user services

Alexis <[email protected]> wrote:
>Hi all,
>
>With OpenRC now supporting user services, has there been any 
>general recommendation that package maintainers try to provide 
>OpenRC user services where appropriate (without that necessarily 
>being _required_)?
>

I plan on adding user services for different GNOME packages where applicable
(I already have for localsearch and gnome-keyring)

>i use OpenRC overall, but because i started using Gentoo before 
>OpenRC user services were available, i manually set up my own set 
>of s6-rc-based user services:
>
>* a D-Bus session bus;
>* an Emacs server instance;
>* PipeWire aand WirePlumber instances;
>* MPD.
>
>There are now user services provided for D-Bus, Emacs, PipeWire, 
>and WirePlumber. However, MPD does not yet provide one (and in the 
>context of my own use-case, i don&#x27;t want to be running MPD as a 
>system service). Nor, for example, is there a user service for 
>media-sound/snapcast - earlier i opened 
>https://bugs.gentoo.org/980076 about the issues this causes in the 
>context of a per-user PipeWire setup, but in the meantime, 
>https://wiki.gentoo.org/wiki/Snapcast has just been updated to 
>tell people to start the `snapserver` process via the relevant GUI 
>startup file. (A wiki contributor had actually said to start it 
>via a terminal, e.g. Konsole, which is even messier.) And after 
>installing media-sound/mpd-mpris from GURU, i found that didn&#x27;t 
>provide a user service either.
>
>This is all understandable given that:
>
>(a) OpenRC user services are still relatively new;
>(b) they&#x27;re unlikely to be provided by upstream; and
>(c) creating OpenRC services will require extra work from package 
>maintainers.
>
>But has there been any general communication along the lines of 
>&quot;Hey, consider creating OpenRC user services&quot;?
>
>If nothing else, lack of OpenRC user services can add significant 
>complications to wiki pages, which end up needing to describe 
>workarounds, ranging from &#x27;basically okay&#x27; to &#x27;questionable at 
>best&#x27;. In the context of systemd, we can usually talk about simple 
>calls to `systemd --user`, but in the absence of OpenRC user 
>services being available for a particular package, such simplicity 
>is not necessarily possible.
>
>As an example, take 
>https://wiki.gentoo.org/wiki/PipeWire#gentoo-pipewire-launcher and 
>the two following sections (&quot;GUI environments&quot;, &quot;Restarting 
>PipeWire and WirePlumber&quot;). Ris, immolo and myself all agree that 
>the &quot;PipeWire&quot; page is too complex as it stands, and having to 
>describe how to set things up in the absence of OpenRC services 
>has contributed to that. With the availability of OpenRC user 
>services for PipeWire and WirePlumber, i&#x27;m thinking the three 
>sections i mentioned could be broken out to a separate page for 
>those who aren&#x27;t using systemd/OpenRC user services, and instead 
>be replaced by straightforward descriptions of enabling and 
>starting those services. (We&#x27;ve also discussed things like 
>breaking other content out to separate pages, such as 
>&quot;Troubleshooting&quot; sections, and i&#x27;m planning to work on that as 
>well.)
>
>Thoughts?
>
>Alexis.