f634d48b7c
Add the ability to include any number of (potentially nested) concrete environments, e.g.: ```yaml spack: specs: [] concretizer: unify: true include_concrete: - /path/to/environment1 - /path/to/environment2 ``` or, from the CLI: ```console $ spack env create myenv $ spack -e myenv add python $ spack -e myenv concretize $ spack env create --include-concrete myenv included_env ``` The contents of included concrete environments' spack.lock files are included in the environment's lock file at creation time. Any changes to included concrete environments are only reflected after the environment is re-concretized from the re-concretized included environments. - [x] Concretize included envs - [x] Save concrete specs in memory by hash - [x] Add included envs to combined env's lock file - [x] Add test - [x] Update documentation Co-authored-by: Kayla Butler <<butler59@llnl.gov> Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.co m> Co-authored-by: Todd Gamblin <tgamblin@llnl.gov> Signed-off-by: Todd Gamblin <tgamblin@llnl.gov> |
||
---|---|---|
.. | ||
bash | ||
bootstrap | ||
csh | ||
docker | ||
docs/docker/module-file-tutorial | ||
fish | ||
gitlab/cloud_pipelines | ||
keys | ||
logo | ||
qa | ||
templates | ||
setup-env.csh | ||
setup-env.fish | ||
setup-env.ps1 | ||
setup-env.sh | ||
setup-tutorial-env.sh | ||
spack-completion.bash | ||
spack-completion.fish |