Skip to content
Snippets Groups Projects
  1. Feb 19, 2024
  2. Feb 09, 2024
    • Simon McVittie's avatar
      Rename PvBwrapLock to SrtFileLock and move it to common code · 9052fbd4
      Simon McVittie authored
      
      This was implemented to interact correctly with the locking scheme
      used in bwrap(1) (which uses the non-OFD flavour of fnctl locks), but
      is otherwise unrelated to bwrap(1) or pressure-vessel. Moving this into
      common code will facilitate using it outside pressure-vessel, in
      particular when unpacking `ubuntu12_64/steam-runtime-sniper/`.
      
      While I'm changing the interface anyway, take the opportunity to rename
      the WRITE flag to EXCLUSIVE, which is clearer.
      
      Helps: steamrt/tasks#387
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      9052fbd4
  3. Feb 02, 2024
  4. Jan 31, 2024
  5. Dec 07, 2023
  6. Nov 22, 2023
  7. Nov 20, 2023
  8. Nov 17, 2023
  9. Nov 16, 2023
  10. Oct 30, 2023
  11. Oct 25, 2023
  12. Oct 19, 2023
  13. Oct 04, 2023
  14. Aug 31, 2023
  15. Aug 30, 2023
  16. Jul 28, 2023
  17. Jun 02, 2023
    • Simon McVittie's avatar
      372c2d1f
    • Simon McVittie's avatar
    • Simon McVittie's avatar
      launcher-service: Add an --alongside-steam option · deacd58b
      Simon McVittie authored
      
      This allows Steam to provide a process-launching service that is outside
      the container runtime (but possibly inside a larger sandbox like Flatpak
      or Snap), allowing game processes to run tools such as mango_intel_stats
      that cannot usefully be run inside the container (steamrt/tasks#293,
      #107).
      
      The intended use is that Steam will run this, with the PATH and
      LD_LIBRARY_PATH of the Steam Runtime 1 'scout' environment in effect:
      
          steam-runtime-launcher-service --alongside-steam
      
      Some defaults change when this option is in use, to be more suitable
      for this use-case.
      
      Steam can optionally set environment variable
      `SRT_LAUNCHER_SERVICE_ALONGSIDE_STEAM` to
      `com.steampowered.PressureVessel.LaunchAlongsideSteam`
      in the environment used to launch games, as a way to signal that this
      mechanism is available.
      
      If desired, Steam can wait for the launcher service to be ready by passing
      a pipe to it as its standard output (fd 1) or as a higher fd referenced by
      the --info-fd option, and then reading from that pipe until end-of-file
      is reached. If it does this before launching any apps or games, then
      apps and games can safely assume that the launcher service is ready for
      immediate use.
      
      Alternatively, Steam can let the launcher service start asynchronously,
      by passing /dev/null as its standard output. If this is done, an app or
      game that starts up very quickly after Steam is launched might find that
      `steam-runtime-launch-client --alongside-steam -- ...` does not work
      until some time has passed.
      
      To the extent that it's possible, launched processes get the same host
      execution environment as the top-level process of Steam itself (the
      bin_steam.sh script); this is similar to what happens for non-Steam
      app shortcuts. They can re-enter the Steam Runtime 1 'scout' environment,
      if desired, by running ~/.steam/root/ubuntu12_32/steam-runtime/run.sh.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      deacd58b
  18. Jun 01, 2023
Loading