diff options
author | Harmen Stoppels <harmenstoppels@gmail.com> | 2023-05-05 19:54:26 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-05 19:54:26 +0200 |
commit | 9ef062fcca4d2fd38b496b2c4e2c8a7e6e97de15 (patch) | |
tree | 20735da170a8bf9af48afe8804b0a172932ea7e3 /.mailmap | |
parent | ddea33bdc0a5cd14ecec700d552455a2ec7ca4de (diff) | |
download | spack-9ef062fcca4d2fd38b496b2c4e2c8a7e6e97de15.tar.gz spack-9ef062fcca4d2fd38b496b2c4e2c8a7e6e97de15.tar.bz2 spack-9ef062fcca4d2fd38b496b2c4e2c8a7e6e97de15.tar.xz spack-9ef062fcca4d2fd38b496b2c4e2c8a7e6e97de15.zip |
Add spack buildcache push (alias to buildcache create) (#34861)
`spack buildcache create` is a misnomer cause it's the only way to push to
an existing buildcache (and it in fact calls binary_distribution.push).
Also we have `spack buildcache update-index` but for create the flag is
`--rebuild-index`, which is confusing (and also... why "rebuild"
something if the command is "create" in the first place, that implies it
wasn't there to begin with).
So, after this PR, you can use either
```
spack buildcache create --rebuild-index
```
or
```
spack buildcache push --update-index
```
Also, alias `spack buildcache rebuild-index` to `spack buildcache
update-index`.
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions