diff options
author | Peter Scheibel <scheibel1@llnl.gov> | 2022-09-01 11:04:01 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-09-01 11:04:01 -0700 |
commit | 2968ae667f62f859f42d08897b0bca273265158d (patch) | |
tree | 060fca33ac8b43572d5172e89bd6d05513bee8cd /bin/spack_pwsh.ps1 | |
parent | 92b72f186e3e7e53e133f41c783739cb26bc7e7c (diff) | |
download | spack-2968ae667f62f859f42d08897b0bca273265158d.tar.gz spack-2968ae667f62f859f42d08897b0bca273265158d.tar.bz2 spack-2968ae667f62f859f42d08897b0bca273265158d.tar.xz spack-2968ae667f62f859f42d08897b0bca273265158d.zip |
New command, `spack change`, to change existing env specs (#31995)
If you have an environment like
```
$ cat spack.yaml
spack:
specs: [openmpi@4.1.0+cuda]
```
this PR provides a new command `spack change` that you can use to adjust environment specs from the command line:
```
$ spack change openmpi~cuda
$ cat spack.yaml
spack:
specs: [openmpi@4.1.0~cuda]
```
in other words, this allows you to tweak the details of environment specs from the command line.
Notes:
* This is only allowed for environments that do not define matrices
* This is possible but not anticipated to be needed immediately
* If this were done, it should probably only be done for "named"/not-anonymous specs (i.e. we can change `openmpi+cuda` but not spec like `+cuda` or `@4.0.1~cuda`)
Diffstat (limited to 'bin/spack_pwsh.ps1')
0 files changed, 0 insertions, 0 deletions