diff options
| author | Dr. Christian Tacke <58549698+ChristianTackeGSI@users.noreply.github.com> | 2020-07-20 22:58:06 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-20 13:58:06 -0700 |
| commit | bd236918dd598e217ca553f1c24780a1411d1c98 (patch) | |
| tree | 860b81e58033cc23cec81f145f38084ed5e78c36 /.github/ISSUE_TEMPLATE | |
| parent | 3949a85f9a75320895c752f95a1c8a7480795110 (diff) | |
| download | spack-bd236918dd598e217ca553f1c24780a1411d1c98.tar.gz spack-bd236918dd598e217ca553f1c24780a1411d1c98.tar.bz2 spack-bd236918dd598e217ca553f1c24780a1411d1c98.tar.xz spack-bd236918dd598e217ca553f1c24780a1411d1c98.zip | |
Configuration: allow usage of command-line scopes with environments (#14608)
Spack did not support usage of the `--config-scope` option in
combination with an environment: In `lib/spack/spack/main.py`,
`spack.config.command_line_scopes` is set equal to any config scopes
passed by the `--config-scope` option. However, this is done after
activating an environment. In the process of activating an environment,
the `spack.config.config` singleton is instantiated, so later setting of
`spack.config.command_line_scopes` is ignored.
This commit sets command line scopes before activating an environment to
ensure that they are included in the configuration.
Co-authored-by: Tim Fuller <tjfulle@sandia.gov>
Diffstat (limited to '.github/ISSUE_TEMPLATE')
0 files changed, 0 insertions, 0 deletions