- Nov 17, 2023
-
-
Simon McVittie authored
This matches the output of bsdtar (libarchive), for example: bsdtar -cf- --format=mtree -C ~/tmp . and NetBSD mtree(8) (the mtree-netbsd package in Debian), for example: mtree -c -p ~/tmp | mtree -C Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 31, 2023
-
-
Simon McVittie authored
We want to use this script with a local build in CI, to integrate it with the actual runtime build (for soldier/sniper) or the steam-runtime-tools build (for scout). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In CI builds, we often know better than `git describe` does. Change the precedence so a new --scripts-version is highest priority, then a .tarball-version file, and finally a version guessed from `git describe`. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Dec 15, 2022
-
-
Simon McVittie authored
If we're using a local or pre-downloaded pressure-vessel-bin.tar.gz, there's no point in trying to download the scout LD_LIBRARY_PATH runtime (for automated testing) from a suite named "local" that doesn't exist. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Dec 14, 2022
-
-
Simon McVittie authored
This allows populate-depot.py to learn its own version number when used by unpacking a steam-runtime-tools source tarball, rather than from git, and write that into VERSIONS.txt as the "scripts" component. Now that we've combined SteamLinuxRuntime and s-r-t into one repository, the "scripts" component is somewhat redundant for the soldier and sniper runtimes (since it will always match up with pressure-vessel), but it's still interesting for the scout-on-soldier runtime (which does not contain its own copy of pressure-vessel). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-