Skip to content
Snippets Groups Projects
  1. Dec 10, 2020
    • Simon McVittie's avatar
      pressure-vessel-wrap: Remove --host-fallback option · 22a1aa68
      Simon McVittie authored
      
      We are not going to be able to do this from within Flatpak, and it is
      unsuitable for running runtimes other than Steam Runtime 1 'scout',
      for which the LD_LIBRARY_PATH runtime mostly already works.
      
      If we need an automatic fallback to running on the host for scout games,
      we can do that better by running `pressure-vessel-wrap --test`.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      22a1aa68
  2. Nov 30, 2020
  3. Nov 24, 2020
  4. 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
  5. Sep 30, 2020
  6. Sep 09, 2020
  7. Sep 08, 2020
  8. Sep 07, 2020
  9. Aug 19, 2020
Loading