diff options
author | Richarda Butler <39577672+RikkiButler20@users.noreply.github.com> | 2024-05-07 09:32:40 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-05-07 09:32:40 -0700 |
commit | be71f9fdc4ae85c4c9644447713ab0916a6348d4 (patch) | |
tree | 8a4a3ac6d70511d155536c28f693d96bc29b79d8 /var | |
parent | 05c1e7ecc22b873c3e534aef45774c88521fe7b3 (diff) | |
download | spack-be71f9fdc4ae85c4c9644447713ab0916a6348d4.tar.gz spack-be71f9fdc4ae85c4c9644447713ab0916a6348d4.tar.bz2 spack-be71f9fdc4ae85c4c9644447713ab0916a6348d4.tar.xz spack-be71f9fdc4ae85c4c9644447713ab0916a6348d4.zip |
Include concrete environments with `include_concrete` (#33768)
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>
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions