diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2023-10-06 10:24:21 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-10-06 10:24:21 +0200 |
commit | e20c05fcdfc7a9ad995956bfee269e123860288f (patch) | |
tree | bb94c72fce83126116e0bcd8561a7c3b560ecc3c /.git-blame-ignore-revs | |
parent | 36183eac408539e84323fe5ec514d7ae83e4bca6 (diff) | |
download | spack-e20c05fcdfc7a9ad995956bfee269e123860288f.tar.gz spack-e20c05fcdfc7a9ad995956bfee269e123860288f.tar.bz2 spack-e20c05fcdfc7a9ad995956bfee269e123860288f.tar.xz spack-e20c05fcdfc7a9ad995956bfee269e123860288f.zip |
Make "minimal" the default duplicate strategy (#39621)
* Allow branching out of the "generic build" unification set
For cases like the one in https://github.com/spack/spack/pull/39661
we need to relax rules on unification sets.
The issue is that, right now, nodes in the "generic build" unification
set are unified together with their build dependencies. This was done
out of caution to avoid the risk of circular dependencies, which would
ultimately cause a very slow solve.
For build-tools like Cython, however, the build dependencies is masked
by a long chain of "build, run" dependencies that belong in the
"generic build" unification space.
To allow splitting on cases like this, we relax the rule disallowing
branching out of the "generic build" unification set.
* Fix issue with pure build virtual dependencies
Pure build virtual dependencies were not accounted properly in the
list of possible virtuals. This caused some facts connecting virtuals
to the corresponding providers to not be emitted, and in the end
lead to unsat problems.
* Fixed a few issues in packages
py-gevent: restore dependency on py-cython@3
jsoncpp: fix typo in build dependency
ecp-data-vis-sdk: update spack.yaml and cmake recipe
py-statsmodels: add v0.13.5
* Make dependency on "blt" of type "build"
Diffstat (limited to '.git-blame-ignore-revs')
0 files changed, 0 insertions, 0 deletions