diff options
| author | Todd Gamblin <gamblin2@llnl.gov> | 2022-02-22 11:35:34 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-22 12:35:34 -0700 |
| commit | 36b0730fac31463b58f5317dbfa60ee28c6e8bb0 (patch) | |
| tree | 7b6dde125e44b0b8b373a879bbfb6325a0e5a4d3 /bin/spack-python | |
| parent | 800933bbdfc4caff6285806249edd20f025fa99b (diff) | |
| download | spack-36b0730fac31463b58f5317dbfa60ee28c6e8bb0.tar.gz spack-36b0730fac31463b58f5317dbfa60ee28c6e8bb0.tar.bz2 spack-36b0730fac31463b58f5317dbfa60ee28c6e8bb0.tar.xz spack-36b0730fac31463b58f5317dbfa60ee28c6e8bb0.zip | |
Add `spack --bootstrap` option for accessing bootstrap store (#25601)
We can see what is in the bootstrap store with `spack find -b`, and you can clean it with `spack
clean -b`, but we can't do much else with it, and if there are bootstrap issues they can be hard to
debug.
We already have `spack --mock`, which allows you to swap in the mock packages from the command
line. This PR introduces `spack -b` / `spack --bootstrap`, which runs all of spack with
`ensure_bootstrap_configuration()` set. This means that you can run `spack -b find`, `spack -b
install`, `spack -b spec`, etc. to see what *would* happen with bootstrap configuration, to remove
specific bootstrap packages, etc. This will hopefully make developers' lives easier as they deal
with bootstrap packages.
This PR also uses a `nullcontext` context manager. `nullcontext` has been implemented in several
other places in Spack, and this PR consolidates them to `llnl.util.lang`, with a note that we can
delete the function if we ever reqyire a new enough Python.
- [x] introduce `spack --bootstrap` option
- [x] consolidated all `nullcontext` usages to `llnl.util.lang`
Diffstat (limited to 'bin/spack-python')
0 files changed, 0 insertions, 0 deletions