diff options
author | Greg Becker <becker33@llnl.gov> | 2023-11-10 14:55:35 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-11-10 14:55:35 -0800 |
commit | 13abfb7013ca282b06cf4069d96c3d7c093bc684 (patch) | |
tree | a5e485bc2775feb36438bde87b00c518b1811deb /.github/CODE_OF_CONDUCT.md | |
parent | b41fc1ec79ee8ebcf439f3e3b9d18989274cc561 (diff) | |
download | spack-13abfb7013ca282b06cf4069d96c3d7c093bc684.tar.gz spack-13abfb7013ca282b06cf4069d96c3d7c093bc684.tar.bz2 spack-13abfb7013ca282b06cf4069d96c3d7c093bc684.tar.xz spack-13abfb7013ca282b06cf4069d96c3d7c093bc684.zip |
`spack deconcretize` command (#38803)
We have two ways to concretize now:
* `spack concretize` concretizes only the root specs that are not concrete in the environment.
* `spack concretize -f` eliminates all cached concretization data and reconcretizes the *entire* environment.
This PR adds `spack deconcretize`, which eliminates cached concretization data for a spec. This allows
users greater control over what is preserved from their `spack.lock` file and what is reused when not
using `spack concretize -f`. If you want to update a spec installed in your environment, you can call
`spack deconcretize` on it, and that spec and any relevant dependents will be removed from the lock file.
`spack concretize` has two options:
* `--root`: limits deconcretized specs to *specific* roots in the environment. You can use this to
deconcretize exactly one root in a `unify: false` environment. i.e., if `foo` root is a dependent
of `bar`, both roots, `spack deconcretize bar` will *not* deconcretize `foo`.
* `--all`: deconcretize *all* specs that match the input spec. By default `spack deconcretize`
will complain about multiple matches, like `spack uninstall`.
Diffstat (limited to '.github/CODE_OF_CONDUCT.md')
0 files changed, 0 insertions, 0 deletions