2021-07-13 07:00:37 +08:00
|
|
|
bootstrap:
|
|
|
|
|
# If set to false Spack will not bootstrap missing software,
|
|
|
|
|
# but will instead raise an error.
|
|
|
|
|
enable: true
|
|
|
|
|
# Root directory for bootstrapping work. The software bootstrapped
|
|
|
|
|
# by Spack is installed in a "store" subfolder of this root directory
|
config: fix `SPACK_DISABLE_LOCAL_CONFIG`, remove `$user_config_path` (#27022)
There were some loose ends left in ##26735 that cause errors when
using `SPACK_DISABLE_LOCAL_CONFIG`.
- [x] Fix hard-coded `~/.spack` references in `install_test.py` and `monitor.py`
Also, if `SPACK_DISABLE_LOCAL_CONFIG` is used, there is the issue that
`$user_config_path`, when used in configuration files, makes no sense,
because there is no user config scope.
Since we already have `$user_cache_path` in configuration files, and since there
really shouldn't be *any* data stored in a configuration scope (which is what
you'd configure in `config.yaml`/`bootstrap.yaml`/etc., this just removes
`$user_config_path`.
There will *always* be a `$user_cache_path`, as Spack needs to write files, but
we shouldn't rely on the existence of a particular configuration scope in the
Spack code, as scopes are configurable, both in number and location.
- [x] Remove `$user_config_path` substitution.
- [x] Fix reference to `$user_config_path` in `etc/spack/deaults/bootstrap.yaml`
to refer to `$user_cache_path`, which is where it was intended to be.
2021-10-29 05:33:44 +08:00
|
|
|
root: $user_cache_path/bootstrap
|
2021-08-19 02:14:02 +08:00
|
|
|
# Methods that can be used to bootstrap software. Each method may or
|
2022-05-25 05:33:52 +08:00
|
|
|
# may not be able to bootstrap all the software that Spack needs,
|
2021-08-19 02:14:02 +08:00
|
|
|
# depending on its type.
|
|
|
|
|
sources:
|
2022-11-03 17:05:03 +08:00
|
|
|
- name: 'github-actions-v0.4'
|
|
|
|
|
metadata: $spack/share/spack/bootstrap/github-actions-v0.4
|
2022-09-02 18:48:46 +08:00
|
|
|
- name: 'github-actions-v0.3'
|
|
|
|
|
metadata: $spack/share/spack/bootstrap/github-actions-v0.3
|
2022-05-25 05:33:52 +08:00
|
|
|
- name: 'spack-install'
|
|
|
|
|
metadata: $spack/share/spack/bootstrap/spack-install
|
2021-08-19 02:14:02 +08:00
|
|
|
trusted:
|
|
|
|
|
# By default we trust bootstrapping from sources and from binaries
|
|
|
|
|
# produced on Github via the workflow
|
2022-11-03 17:05:03 +08:00
|
|
|
github-actions-v0.4: true
|
2022-09-02 18:48:46 +08:00
|
|
|
github-actions-v0.3: true
|
config: fix `SPACK_DISABLE_LOCAL_CONFIG`, remove `$user_config_path` (#27022)
There were some loose ends left in ##26735 that cause errors when
using `SPACK_DISABLE_LOCAL_CONFIG`.
- [x] Fix hard-coded `~/.spack` references in `install_test.py` and `monitor.py`
Also, if `SPACK_DISABLE_LOCAL_CONFIG` is used, there is the issue that
`$user_config_path`, when used in configuration files, makes no sense,
because there is no user config scope.
Since we already have `$user_cache_path` in configuration files, and since there
really shouldn't be *any* data stored in a configuration scope (which is what
you'd configure in `config.yaml`/`bootstrap.yaml`/etc., this just removes
`$user_config_path`.
There will *always* be a `$user_cache_path`, as Spack needs to write files, but
we shouldn't rely on the existence of a particular configuration scope in the
Spack code, as scopes are configurable, both in number and location.
- [x] Remove `$user_config_path` substitution.
- [x] Fix reference to `$user_config_path` in `etc/spack/deaults/bootstrap.yaml`
to refer to `$user_cache_path`, which is where it was intended to be.
2021-10-29 05:33:44 +08:00
|
|
|
spack-install: true
|