- Nov 17, 2022
-
-
Simon McVittie authored
This redirects output produced by pv-wrap, but puts back the original stdout/stderr for the wrapped program (typically the actual game). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 10, 2022
-
-
Simon McVittie authored
This reduces the chance of getting the three paths confused: we'll do all I/O relative to the fd, and only use the two paths to form bwrap arguments. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 07, 2022
-
-
Simon McVittie authored
Recent Meson versions have warnings if you add the subprojects directory as an include path, because the way Meson wants to consume subprojects is by the subproject's build system producing a Meson dependency object that encapsulates its include directory. libglnx seems to be set up to have the libglnx directory be its include path instead: for example, ostree (by the author of libglnx) already uses "libglnx.h" or <libglnx.h> everywhere. Do the same here. Flatpak equivalent: https://github.com/flatpak/flatpak/pull/4842 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 14, 2021
-
-
Simon McVittie authored
This allows developers to access debugfs, event tracing or similar facilities, if allowed by filesystem permissions. This seems risky to support for production use, since it would potentially let games do things that are not long-term supportable, so gate it behind an option equivalent to `flatpak run --devel`. I've made the option generic so that we can use it to gate other similar features in future. Note that programs inside the pressure-vessel container cannot run setuid, setgid or setcap executables for technical reasons. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 05, 2021
-
-
Simon McVittie authored
The environment variables we have built up in `bwrap` are appropriate for the container itself, but inappropriate for the environment in which we run pressure-vessel-launch to ask Flatpak on the host to run bwrap. Keep them more carefully separate. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 25, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 09, 2020
-
-
Simon McVittie authored
This is preparation for combining pressure-vessel with steam-runtime-tools. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 02, 2020
-
-
Ludovico de Nittis authored
The filesystem that is providing /usr might not be mounted in the same place in the current namespace, and on the host system where bwrap will be run. If it isn't, we need to use one path to do file I/O when inspecting it, but pass a different path to bwrap. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jul 29, 2020
-
-
Simon McVittie authored
If the wrapped command prints structured data to stdout, we don't want to corrupt its output stream. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 04, 2020
-
-
Simon McVittie authored
This sketches out roughly how we'd do this if we were in a container such as a Flatpak environment, rather than on the host system. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 23, 2020
-
-
Simon McVittie authored
This makes us match how Flatpak includes it, which makes our versions of Flatpak files more similar. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 11, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 10, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 04, 2019
-
-
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>
-
- May 10, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-