summaryrefslogtreecommitdiff
path: root/COPYRIGHT
diff options
context:
space:
mode:
authorKayla Butler <butler59@llnl.gov>2022-03-28 14:18:00 -0700
committerTodd Gamblin <tgamblin@llnl.gov>2022-11-02 09:43:57 -0700
commitbc209c470d07621ba9af277dab71d048d11f2844 (patch)
tree8f48e8785c9462d97046f5bb67ddd30ab4e6ab1f /COPYRIGHT
parentae99829af4393295953afa0f08394bdcd2b58b75 (diff)
downloadspack-bc209c470d07621ba9af277dab71d048d11f2844.tar.gz
spack-bc209c470d07621ba9af277dab71d048d11f2844.tar.bz2
spack-bc209c470d07621ba9af277dab71d048d11f2844.tar.xz
spack-bc209c470d07621ba9af277dab71d048d11f2844.zip
flags/variants: Add ++/~~/== syntax for propagation to dependencies
Currently, compiler flags and variants are inconsistent: compiler flags set for a package are inherited by its dependencies, while variants are not. We should have these be consistent by allowing for inheritance to be enabled or disabled for both variants and compiler flags. - [x] Make new (spec language) operators - [x] Apply operators to variants and compiler flags - [x] Conflicts currently result in an unsatisfiable spec (i.e., you can't propagate two conflicting values) What I propose is using two of the currently used sigils to symbolized that the variant or compiler flag will be inherited: Example syntax: - `package ++variant` enabled variant that will be propagated to dependencies - `package +variant` enabled variant that will NOT be propagated to dependencies - `package ~~variant` disabled variant that will be propagated to dependencies - `package ~variant` disabled variant that will NOT be propagated to dependencies - `package cflags==True` `cflags` will be propagated to dependencies - `package cflags=True` `cflags` will NOT be propagated to dependencies Syntax for string-valued variants is similar to compiler flags.
Diffstat (limited to 'COPYRIGHT')
0 files changed, 0 insertions, 0 deletions