| commit | 5a6ece397e36365b2b377ec4b7dbf57265b648c3 | |
| author | M. Eric Irrgang <ericirrgang@gmail.com> | |
| Wed, 1 Apr 2020 12:45:36 +0000 (1 15:45 +0300) | ||
| committer | M. Eric Irrgang <ericirrgang@gmail.com> | |
| Wed, 1 Apr 2020 12:46:21 +0000 (1 15:46 +0300) | ||
| tree | 82b29ae214644e8f219493aee2e7872fefc584d7 | treesnapshot (tar.gz zip) |
| parent | de50958390b248fcf837bb196512762ad6e50ca8 | commitdiff |
Avoid accidentally initializing pyenv in CI images.
Don't initialize pyenv automatically in root login shells: don't copy
the updated `.bashrc` from the intermediate build images to the final
image. This can cause confusion about which Python installation can or
will be detected by CMake in a CI job.
The primary use case for `pyenv` is to prepare Python venvs, which are
activated explicitly when needed, and which (once created) do not
require pyenv to be initialized in order to be activated.
Don't initialize pyenv automatically in root login shells: don't copy
the updated `.bashrc` from the intermediate build images to the final
image. This can cause confusion about which Python installation can or
will be detected by CMake in a CI job.
The primary use case for `pyenv` is to prepare Python venvs, which are
activated explicitly when needed, and which (once created) do not
require pyenv to be initialized in order to be activated.
| admin/containers/scripted_gmx_docker_builds.py | diffblobblamehistory |