Skip to content
Snippets Groups Projects
  1. Oct 28, 2022
  2. Jul 20, 2021
    • Simon McVittie's avatar
      pressure-vessel: Remove the concept of "locking" environment variables · feb92d87
      Simon McVittie authored
      
      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: default avatarSimon McVittie <smcv@collabora.com>
      feb92d87
  3. Jul 05, 2021
  4. Jan 05, 2021
    • Simon McVittie's avatar
      pressure-vessel: Move environment variables into new PvEnviron object · 920e32fe
      Simon McVittie authored
      
      This keeps track of environment variables' values and their locked
      status in one place. We build it up over time, and then serialize it
      into final_argv->envp.
      
      In particular, this is a step towards no longer storing anything in the
      variable named bwrap except for bubblewrap options, which will be
      a necessary piece of refactoring when we move to launching the game
      as a Flatpak sub-sandbox, without ever invoking bubblewrap ourselves.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      920e32fe
Loading