diff options
| author | Peter Scheibel <scheibel1@llnl.gov> | 2024-03-29 09:36:31 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-03-29 09:36:31 -0700 |
| commit | 179e4f3ad138c664dd0387e2998d87895e744518 (patch) | |
| tree | 263146c8061153a4f9b954ac6f568403323f3407 /.mailmap | |
| parent | e97787691b78f5745318b571be7ce0296af1a698 (diff) | |
| download | spack-179e4f3ad138c664dd0387e2998d87895e744518.tar.gz spack-179e4f3ad138c664dd0387e2998d87895e744518.tar.bz2 spack-179e4f3ad138c664dd0387e2998d87895e744518.tar.xz spack-179e4f3ad138c664dd0387e2998d87895e744518.zip | |
Don't delete "spack develop" build artifacts after install (#43424)
After #41373, where we stopped considering the source directory to be the stage for develop builds,
we resumed *deleting* the stage even after a successful build.
We don't want this for develop builds because developers need to iterate; we should keep the artifacts
unless they explicitly run `spack clean`.
Now:
- [x] Build artifacts for develop packages are not removed after a successful install
- [x] They are also not removed before an install starts, i.e. develop packages always
reuse prior artifacts, if available.
- [x] They can be deleted in any other context, e.g. by running `spack clean --stage`
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions