Skip to content

Use steam-runtime-launcher-interface-0

Simon McVittie requested to merge wip/smcv/simpler-launcher-service into master

  • common: Try to use steam-runtime-launcher-interface-0

    This is a simplified interface for applying the policy for whether to set up a launcher-service: we just need to be able to find it.

  • scout-on-soldier: Try to use steam-runtime-launcher-interface-0

    If we're running in a sufficiently new soldier container, then this will be in the PATH.

  • Add compatmanager_layer_name to toolmanifest.vdf

    As agreed in https://github.com/ValveSoftware/Proton/pull/5891.

This assumes the interface from steam-runtime-tools!465 (merged).

Until steam-runtime-tools!465 (merged) gets into soldier/sniper releases and the necessary integration gets into the Steam client, you can test this by:

  • when injecting commands into the soldier/sniper environment (container-runtime layer): replace SteamLinuxRuntime_*/pressure-vessel with a build from steam-runtime-tools!465 (merged), and put STEAM_COMPAT_LAUNCHER_SERVICE=container-runtime in Steam's environment or the Launch Options

  • when injecting commands into the scout environment: replace SteamLinuxRuntime_*/pressure-vessel with a build from steam-runtime-tools!465 (merged), put STEAM_COMPAT_LAUNCHER_SERVICE=scout-in-container and PRESSURE_VESSEL_SHELL=instead in Steam's environment or the Launch Options, and when the xterm pops up, export PATH=/run/pressure-vessel/pv-from-host/bin:$PATH before running "$@"

Edited by Simon McVittie

Merge request reports