Remove "session mode"
- Jul 20, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We used to use this to process Windows games' installscripts, but since Steam beta 1623823138, Steam implements a much simpler interface for running installscripts and we don't need this any more. Less code means fewer bugs! Instead of doing all the previous logic with commands run in the background, we just call exec_container. See also steam-runtime-tools!324, which documents the old and new compatibility tool interfaces. Resolves: T28961 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This effectively hard-codes PRESSURE_VESSEL_RELAUNCH_CONTAINER to 1: if we are in "session mode" with a STEAM_COMPAT_SESSION_ID set, then we will still share a container started by _start-container-in-background between one or more setup commands, but then we will terminate that container and start again for the actual game. We need to do this if we want the actual game to be able to take its user-specified launch options into account, which is why it has been the default since January. Part of T25709. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-