-
- Downloads
pressure-vessel: Remove the concept of "locking" environment variables
This was only necessary because we were reusing a single container
across multiple entry-point invocations, and expecting "most" arbitrary
environment variables from each new invocation to be taken into account
for commands running in the container, which meant that we needed to
keep track of which environment variables had to be exceptions to that
rule for technical reasons. Now that we're no longer injecting multiple
commands into the same container like that, we don't need this
complexity.
Signed-off-by:
Simon McVittie <smcv@collabora.com>
parent
c9b2f9c2
No related branches found
No related tags found
Showing
- pressure-vessel/environ.c 11 additions, 71 deletionspressure-vessel/environ.c
- pressure-vessel/environ.h 5 additions, 11 deletionspressure-vessel/environ.h
- pressure-vessel/launcher.1.md 1 addition, 8 deletionspressure-vessel/launcher.1.md
- pressure-vessel/launcher.c 2 additions, 65 deletionspressure-vessel/launcher.c
- pressure-vessel/runtime.c 22 additions, 22 deletionspressure-vessel/runtime.c
- pressure-vessel/wrap-pipewire.c 3 additions, 3 deletionspressure-vessel/wrap-pipewire.c
- pressure-vessel/wrap-setup.c 6 additions, 6 deletionspressure-vessel/wrap-setup.c
- pressure-vessel/wrap.c 22 additions, 60 deletionspressure-vessel/wrap.c
Loading
Please register or sign in to comment