diff options
| author | Greg Becker <becker33@llnl.gov> | 2020-03-31 16:09:08 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-31 16:09:08 -0700 |
| commit | 336191c25145823be104011fda23651e6e6aa723 (patch) | |
| tree | 9b3f3c15ec03c9c75d3d8d1d55db024690081a90 /var | |
| parent | 87481609845310c3cb2a7bc324beeffe1c38f4b3 (diff) | |
| download | spack-336191c25145823be104011fda23651e6e6aa723.tar.gz spack-336191c25145823be104011fda23651e6e6aa723.tar.bz2 spack-336191c25145823be104011fda23651e6e6aa723.tar.xz spack-336191c25145823be104011fda23651e6e6aa723.zip | |
packages.yaml: allow virtuals to specify buildable: false (#14934)
Currently, to force Spack to use an external MPI, you have to specify `buildable: False`
for every MPI provider in Spack in your packages.yaml file. This is both tedious and
fragile, as new MPI providers can be added and break your workflow when you do a
git pull.
This PR allows you to specify an entire virtual dependency as non-buildable, and
specify particular implementations to be built:
```
packages:
all:
providers:
mpi: [mpich]
mpi:
buildable: false
paths:
mpich@3.2 %gcc@7.3.0: /usr/packages/mpich-3.2-gcc-7.3.0
```
will force all Spack builds to use the specified `mpich` install.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions