Add steam-runtime-launcher-service integration
Compare changes
_v2-entry-point: Fix a shellcheck warning
In principle ${STEAM_RUNTIME} could include wildcards, which we want taken literally.
Add basic steam-runtime-launcher-service integration
If run with STEAM_COMPAT_LAUNCHER_SERVICE=container-runtime
, we'll
inject commands at the container layer and they'll run in a "pure"
soldier/sniper environment. This is appropriate for native soldier/sniper
games that run with no further compatibility layer, as in
ValveSoftware/steam-runtime#508.
If run with STEAM_COMPAT_LAUNCHER_SERVICE=scout-in-container
, we'll
inject commands inside the layered scout-on-soldier runtime (or
potentially scout-on-sniper, if we pivot to that at some point) and
they'll run in a scout-compatible environment.
Add app-ID-based triggering for steam-runtime-launcher-service
The idea here is that Steam would set
STEAM_COMPAT_LAUNCHER_SERVICE=1628350
to get a way to inject commands
at the sniper container runtime layer, and so on.
jupiter/tasks#483