diff options
| author | Peter Scheibel <scheibel1@llnl.gov> | 2019-06-08 11:43:26 -0700 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2019-06-08 11:43:26 -0700 |
| commit | f31711b84e4ce9c34b845c2061f23829154b7069 (patch) | |
| tree | 033203b05a099c48a64dcda18ad1865763951cf8 /share | |
| parent | bdf831469a212d98ac86834182e460349daf8275 (diff) | |
| download | spack-f31711b84e4ce9c34b845c2061f23829154b7069.tar.gz spack-f31711b84e4ce9c34b845c2061f23829154b7069.tar.bz2 spack-f31711b84e4ce9c34b845c2061f23829154b7069.tar.xz spack-f31711b84e4ce9c34b845c2061f23829154b7069.zip | |
concretization: don't apply build-dep constraints for installed packages (#11594)
Spack currently tries to unify everything in the DAG, but this is too strict for build dependencies, where it is fine to build a dependency with a tool that conflicts with a version fo that tool for a dependent's build.
To enable a workaround for conflicts among build dependencies, so that users can install in multiple steps to avoid these conflicts, make the following changes:
* Dont apply package dependency constraints for build deps of installed packages
* Avoid applying constraints for installed packages vs. concrete packages
* Mark all dependencies of installed packages as visited in normalization method
* don't remove dependency links for concrete specs in flat_dependencies
Also add tests:
* Update test to ensure that link dependencies of installed packages have constraints applied
* Add test to check for proper handling of transitive dependencies (which is currently not the case)
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions