What are the best practices for a "wayland" user runlevel?

[sbrudenell]

hi,

per #723 (comment) and #925 (comment), i see that for user services that must be run under wayland (like xdg-desktop-portal-wlr), the current best practice is a setup like this:

# make a "wayland" user runlevel
mkdir -p ~/.config/rc/runlevels/wayland

# add any wayland-dependent services to the "wayland" runlevel
rc-update --user add xdg-desktop-portal-wlr wayland

# allow openrc to see $WAYLAND_DISPLAY (unnecessary in openrc-0.64?)
echo rc_env_allow="WAYLAND_DISPLAY" >> ~/.config/rc/rc.conf

# add any other services in the "default" runlevel to "wayland" as well
rc-update --user add ssh-agent default wayland

# enter the `wayland` runlevel from within the compositor
echo exec openrc --user wayland >> ~/.config/sway/config

is all of that right?

is there a best practice or proposal for how to exit the wayland runlevel?

in sway's case I see there's no way to run a command at exit, and the only workaround is asynchronous (swaywm/sway#7128 (comment)). an asynchronous openrc --user default might run after pam_openrc exits which is bad.

in my testing it looks like this is mostly fine.

if i do:

• log into a VT
• log into sway in my display manager
• exit sway
• check rc-status --user: I see xdg-desktop-portal-wlr eventually marked as [ failed ]
• log back into sway
• check rc-status --user again: I see xdg-desktop-portal-wlr is restarted, apparently openrc --user wayland restarts the failed service

but, i can imagine race conditions where xdg-desktop-portal-wlr doesn't get restarted.

would it be More Correct to have ~/.config/sway/config look like:

exec openrc --user default
exec openrc --user wayland

?