diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2024-11-04 07:35:16 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-03 22:35:16 -0800 |
commit | 395c911689d7a3ee426660f3fab334ccee04da1a (patch) | |
tree | 7a348345c3e80e2cfc9f9b52a52ef023fff2f821 /var | |
parent | 2664303d7acf831f84566e7275d8d4a233ab5a46 (diff) | |
download | spack-395c911689d7a3ee426660f3fab334ccee04da1a.tar.gz spack-395c911689d7a3ee426660f3fab334ccee04da1a.tar.bz2 spack-395c911689d7a3ee426660f3fab334ccee04da1a.tar.xz spack-395c911689d7a3ee426660f3fab334ccee04da1a.zip |
Specs: propagated variants affect `==` equality (#47376)
This PR changes the semantic of == for spec so that:
hdf5++mpi == hdf5+mpi
won't hold true anymore. It also changes the constrain semantic, so that a
non-propagating variant always override a propagating variant. This means:
(hdf5++mpi).constrain(hdf5+mpi) -> hdf5+mpi
Before we had a very weird semantic, that was supposed to be tested by unit-tests:
(libelf++debug).constrain(libelf+debug+foo) -> libelf++debug++foo
This semantic has been dropped, as it was never really tested due to the == bug.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions