summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorMichael Kuhn <michael.kuhn@ovgu.de>2020-11-18 12:20:56 +0100
committerGitHub <noreply@github.com>2020-11-18 03:20:56 -0800
commit20367e472d780d4090c6343a9af2000d01997f8a (patch)
treecedec400e1068494d1e1a05746a226b4a7ac7aac /.github
parent77b2e578ec47f7713cae965fede1ab6e60aa69c4 (diff)
downloadspack-20367e472d780d4090c6343a9af2000d01997f8a.tar.gz
spack-20367e472d780d4090c6343a9af2000d01997f8a.tar.bz2
spack-20367e472d780d4090c6343a9af2000d01997f8a.tar.xz
spack-20367e472d780d4090c6343a9af2000d01997f8a.zip
cmd: add `spack mark` command (#16662)
This adds a new `mark` command that can be used to mark packages as either explicitly or implicitly installed. Apart from fixing the package database after installing a dependency manually, it can be used to implement upgrade workflows as outlined in #13385. The following commands demonstrate how the `mark` and `gc` commands can be used to only keep the current version of a package installed: ```console $ spack install pkgA $ spack install pkgB $ git pull # Imagine new versions for pkgA and/or pkgB are introduced $ spack mark -i -a $ spack install pkgA $ spack install pkgB $ spack gc ``` If there is no new version for a package, `install` will simply mark it as explicitly installed and `gc` will not remove it. Co-authored-by: Greg Becker <becker33@llnl.gov>
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions