diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2022-05-12 13:24:08 +1000 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2022-05-19 15:24:15 +0200 |
commit | 14cbbd602c82bc48df8b0a942f1198537aeced78 (patch) | |
tree | 744010c1b668ac0e0e8049fc3e4c42de42986863 /test/distro/debian | |
parent | 5f637a2060b21388314eeb1a7e6d7f349cd11142 (diff) | |
download | passt-14cbbd602c82bc48df8b0a942f1198537aeced78.tar passt-14cbbd602c82bc48df8b0a942f1198537aeced78.tar.gz passt-14cbbd602c82bc48df8b0a942f1198537aeced78.tar.bz2 passt-14cbbd602c82bc48df8b0a942f1198537aeced78.tar.lz passt-14cbbd602c82bc48df8b0a942f1198537aeced78.tar.xz passt-14cbbd602c82bc48df8b0a942f1198537aeced78.tar.zst passt-14cbbd602c82bc48df8b0a942f1198537aeced78.zip |
tests: Don't use tmux update-environment
The semantics of tmux's update-environment option are a bit confusing.
It says it means the given variables are copied into the session
environment from the source environment, but it's not entirely clear
what the "source" environment means.
From my experimentation it appeast to be the environment from which
the tmux *server* is launched, not the one issuing the 'new-session'
command. That makes it pretty much useles, certainly in our case where
we have no way of knowing if the user has pre-existing tmux sessions.
Instead use the new-session -e option to explicitly pass in the variables
we want to propagate.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'test/distro/debian')
0 files changed, 0 insertions, 0 deletions