Skip to content
Snippets Groups Projects
  1. Oct 19, 2020
  2. Oct 08, 2020
  3. Oct 07, 2020
  4. Oct 06, 2020
  5. Oct 05, 2020
  6. Oct 02, 2020
  7. Oct 01, 2020
    • Simon McVittie's avatar
      launcher: Always set PWD to the command's actual working directory · e71023ff
      Simon McVittie authored
      
      pressure-vessel-wrap unsets PWD, but we don't want the command to inherit
      a value of PWD from the launcher. In particular, when running in session
      mode, the launcher's $PWD is the Steam installation, typically
      ~/.local/share/Steam, and the setup commands are also run with that
      working directory, but the actual game is run with the current working
      directory set to its own game directory (which we didn't necessarily
      even know at the time that the launcher was started).
      
      Consumers of $PWD should really check that it is equivalent to the
      actual current working directory and ignore it if it does not, like
      GNU get_current_dir_name(3) and our pv_get_current_dirs() do, but
      blindly believing $PWD is a common shell-scripting mistake, and I
      wouldn't be surprised if there are some games whose launcher scripts
      will believe $PWD even when it doesn't coincide with the real working
      directory.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      e71023ff
    • Simon McVittie's avatar
      Merge branch 'wip/denittis/t22371_custom_vars' into 'master' · 1bde4ae9
      Simon McVittie authored
      Add an environment variables locking system
      
      Closes #17
      
      See merge request steam/steam-runtime-tools!134
      1bde4ae9
    • Ludovico de Nittis's avatar
      Add an environment variables locking system · d7a6aebb
      Ludovico de Nittis authored
      
      If we want to pass all the possible variables that a user might have set
      in its environment, we need a mechanism to lock the variables that
      pressure-vessel is editing (e.g. LIBGL_DRIVERS_PATH), variables that we
      want to keep unset because will be wrong in the new container (e.g.
      FLATPAK_ID) and variables that should inherit their value from the host
      system (e.g. DISPLAY).
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      d7a6aebb
  8. Sep 30, 2020
  9. Sep 29, 2020
Loading