diff options
author | Abhik Sarkar <62109745+asarkar-parsys@users.noreply.github.com> | 2022-03-17 16:42:07 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-03-17 17:42:07 -0600 |
commit | 0ce8b9d3983acaf2469b3b10af8bd1b72798026b (patch) | |
tree | 080b8498f9bbe8777be3279dd3a6a385b3396adb /bin/haspywin.py | |
parent | f8f4aafe8134a859c751ea6a7698aa936eed48a6 (diff) | |
download | spack-0ce8b9d3983acaf2469b3b10af8bd1b72798026b.tar.gz spack-0ce8b9d3983acaf2469b3b10af8bd1b72798026b.tar.bz2 spack-0ce8b9d3983acaf2469b3b10af8bd1b72798026b.tar.xz spack-0ce8b9d3983acaf2469b3b10af8bd1b72798026b.zip |
Make boost minimal and composable (Original PR#22303) (#28623)
* Make boost composable
Currently Boost enables a few components through variants by default,
which means that if you want to use only what you need and no more, you
have to explicitly disable these variants, leading to concretization
errors whenever a second package explicitly needs those components.
For instance if package A only needs `+component_a` it might depend on
`boost +component_a ~component_b`. And if packge B only needs
`+component_b` it might depend on `boost ~component_a +component_b`. If
package C now depends on both A and B, this leads to unsatisfiable
variants and hence a concretization error.
However, if we default to disabling all components, package A can simply
depend on `boost +component_a` and package B on `boost +component_b` and
package C will concretize to depending on `boost +component_a
+component_b`, and whatever you install, you get the bare minimum.
* Fix style
* Added composable boost dependencies for folly
* fixing akantu merge issue
* hpctoolkit boost dependencies already defined
* Fix Styles
* Fixup style once more
* Adding isort fix
* isort one more time
* Fix for package audit issue
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
Co-authored-by: Ryan O'Malley <rd.omalley@comcast.net>
Diffstat (limited to 'bin/haspywin.py')
0 files changed, 0 insertions, 0 deletions