diff options
author | Peter Scheibel <scheibel1@llnl.gov> | 2022-08-16 11:44:30 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-08-16 11:44:30 -0700 |
commit | 8281a0c5feabfc4fe180846d6fe95cfe53420bc5 (patch) | |
tree | ecf8d87450b065195cdc3a1eccabaeb92c1ca51a /COPYRIGHT | |
parent | 0d981a012d67e9532f42b6f5b0d0bb1e25ec3897 (diff) | |
download | spack-8281a0c5feabfc4fe180846d6fe95cfe53420bc5.tar.gz spack-8281a0c5feabfc4fe180846d6fe95cfe53420bc5.tar.bz2 spack-8281a0c5feabfc4fe180846d6fe95cfe53420bc5.tar.xz spack-8281a0c5feabfc4fe180846d6fe95cfe53420bc5.zip |
Configuration: allow users to enforce hard spec constraints (#27987)
Spack doesn't have an easy way to say something like "If I build
package X, then I *need* version Y":
* If you specify something on the command line, then you ensure
that the constraints are applied, but the package is always built
* Likewise if you `spack add X...`` to your environment, the
constraints are guaranteed to hold, but the environment always
builds the package
* You can add preferences to packages.yaml, but these are not
guaranteed to hold (Spack can choose other settings)
This commit adds a 'require' subsection to packages.yaml: the
specs added there are guaranteed to hold. The commit includes
documentation for the feature.
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
Diffstat (limited to 'COPYRIGHT')
0 files changed, 0 insertions, 0 deletions