-
- Downloads
launcher: Always set PWD to the command's actual working directory
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:
Simon McVittie <smcv@collabora.com>
Showing
- pressure-vessel/launch.1.md 8 additions, 0 deletionspressure-vessel/launch.1.md
- pressure-vessel/launcher.1.md 6 additions, 0 deletionspressure-vessel/launcher.1.md
- pressure-vessel/launcher.c 19 additions, 0 deletionspressure-vessel/launcher.c
- pressure-vessel/wrap.1.md 7 additions, 0 deletionspressure-vessel/wrap.1.md
Loading
Please register or sign in to comment