diff options
author | Harmen Stoppels <me@harmenstoppels.nl> | 2023-11-30 18:38:05 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-11-30 09:38:05 -0800 |
commit | d436e97fc6163ffda9c9b5a8f829dd77484d625d (patch) | |
tree | 65dbef84739d0fe6745c1d478e6609f956f9326d /CHANGELOG.md | |
parent | f3983d60c26a18d5294fdebc6f6ea1b92766a5aa (diff) | |
download | spack-d436e97fc6163ffda9c9b5a8f829dd77484d625d.tar.gz spack-d436e97fc6163ffda9c9b5a8f829dd77484d625d.tar.bz2 spack-d436e97fc6163ffda9c9b5a8f829dd77484d625d.tar.xz spack-d436e97fc6163ffda9c9b5a8f829dd77484d625d.zip |
reuse concretization: allow externals from remote when locally configured (#35975)
This looks to me like the best compromise regarding externals in a
build cache. I wouldn't want `spack install` on my machine to install
specs that were marked external on another. At the same time there are
centers that control the target systems on which spack is used, and
would want to use external in buildcaches.
As a solution, reuse concretization will now consider those externals
used in buildcaches that match a locally configured external in
packages.yaml.
So for example person A installs and pushes specs with this config:
```yaml
packages:
ncurses:
externals:
- spec: ncurses@6.0.12345 +feature
prefix: /usr
```
and person B concretizes and installs using that buildcache with the
following config:
```yaml
packages:
ncurses:
externals:
- spec: ncurses@6
prefix: /usr
```
the spec will be reused (or rather, will be considered for reuse...)
Diffstat (limited to 'CHANGELOG.md')
0 files changed, 0 insertions, 0 deletions