- Aug 03, 2021
-
-
Ludovico de Nittis authored
This reverts commit f32f230a. Since the steam-runtime PR #439 the STEAM_COMPAT_FLAGS options are now a responsibility of run.sh Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Simon McVittie authored
pv-wrap: Generalize SHARED_LIBRARY_GUARD_CONFIG handling See merge request !349
-
Simon McVittie authored
PvRuntime: Factor out the list of supported architectures See merge request !348
-
Simon McVittie authored
We didn't handle the case where SHARED_LIBRARY_GUARD_CONFIG is already set to a custom value. It could conceivably also be in /usr or /lib*, which need the same remapping. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This avoids having two different tables of supported architectures: we can just add gameoverlayrenderer_dir to the table we already have. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We can share this between PvRuntime and pv-adverb, which both want to know overlapping sets of details of known architectures. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Further preparation for !337 See merge request !347
-
Simon McVittie authored
We only need to do this once, and it's harmless to do this even if libshared-library-guard isn't even in use, so we might as well move it out of the loops. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
I think this makes it a bit clearer what's going on: we populate one list (currently a PreloadModule[]) from the command-line options, then translate it to form a second list (in -wrap it's a plain GPtrArray, in -adverb it's implicit in the environment variables we're setting). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This provides some more design-for-test that we can use when unit-testing wrap-setup.c. Forwarded: https://github.com/flatpak/flatpak/pull/4352 Applied-upstream: 1.11.3, commit:c392e5ad Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Three nested loops with non-indicative iterator names are enough to get confusing, so let's index this array with an iterator with a meaningful name. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
launch: Show more explanatory message if Flatpak is using setuid bwrap See merge request !345
-
Simon McVittie authored
build: Separate most of pv-wrap into a convenience library See merge request !346
-
Simon McVittie authored
Equivalent to <https://github.com/flatpak/flatpak-xdg-utils/pull/54 > in flatpak-spawn. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This will test us add coverage for some of its code. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Use more glibc executables from provider when appropriate See merge request !344
-
- Aug 02, 2021
-
-
Simon McVittie authored
Resolves: T29581 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
runtime: Delete overridden libraries from the correct "mesa" path See merge request !342
-
Ludovico de Nittis authored
g_string_replace: Backport from GLib See merge request !343
-
Simon McVittie authored
Note that this implementation does not cope gracefully with zero-length patterns (https://gitlab.gnome.org/GNOME/glib/-/issues/2452 ) so we should be careful not to use it like that. For the use-case that I have in mind, that won't be a problem. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 29, 2021
-
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
flatpak-exports: Update to flatpak 1.11.2 See merge request !341
-
- Jul 28, 2021
-
-
Simon McVittie authored
With the previous two commits, we are in sync with 1.11.2. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
/usr/local points to ../var/usrlocal on Fedora Silverblue. Originally Flatpak commits 3aaea7d2 and 97d1eb84, thanks to Casey Jao and Alexander Larsson. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Originally commit 08f69296 in Flatpak. Thanks to Phaedrus Leeds. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
tests: Link pressure-vessel tests to static libsteam-runtime-tools See merge request !340
-
Simon McVittie authored
We were linking these both statically and dynamically, so it's anyone's guess which one would end up implementing each symbol. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This makes it consistent with what we do when building official packages. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Update libcapsule to v0.20210728.0 See merge request !339
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 22, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
pv-runtime: Don't rewrite /nix/store/... to /run/host/nix/store/... See merge request !336
-
Simon McVittie authored
Previously, we assumed that if OS files on the provider are in a location that is not /usr or a related directory, for example if the OS has /lib/ld-linux.so.2 -> /some/odd/path/i386/ld.so, then they will appear below the same path_in_container_ns as /usr, for example /run/host/some/odd/path/i386/ld.so. However, nothing sets this up for directories other than /usr, /lib*, /bin, /sbin and /etc, so it's a bad assumption. A previous commit handled /etc by redirecting it to /run/host/etc, /run/parent/etc or /run/gfx/etc as appropriate, so we don't need to worry about that here. For the rest, assume that if they appear in the container at all, they'll appear at a path that matches their location in the provider. For the common case where provider = host, which is the only one where we really need to support non-FHS layouts, this means that users can work around lack of explicit support for a particular non-FHS directory with something like PRESSURE_VESSEL_FILESYSTEMS_RO=/some/odd/path. In particular, if we didn't have explicit support for /nix, NixOS users would have been able to use that workaround to get it mounted. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If the realpath() of an OS file is below /etc, each of our code paths ends up with it visible below /run/host/etc, /run/parent/etc or /run/gfx/etc, as appropriate. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-