From f7258e246fdf836a69c3dfba403e42f780f679db Mon Sep 17 00:00:00 2001 From: Harmen Stoppels Date: Mon, 23 May 2022 22:20:34 +0200 Subject: Deprecate `spack:concretization` over `concretizer:unify` (#30038) * Introduce concretizer:unify option to replace spack:concretization * Deprecate concretization * Make spack:concretization overrule concretize:unify for now * Add environment update logic to move from spack:concretization to spack:concretizer:reuse * Migrate spack:concretization to spack:concretize:unify in all locations * For new environments make concretizer:unify explicit, so that defaults can be changed in 0.19 --- etc/spack/defaults/concretizer.yaml | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'etc') diff --git a/etc/spack/defaults/concretizer.yaml b/etc/spack/defaults/concretizer.yaml index 643107d3c0..7311354c28 100644 --- a/etc/spack/defaults/concretizer.yaml +++ b/etc/spack/defaults/concretizer.yaml @@ -28,3 +28,9 @@ concretizer: # instance concretize with target "icelake" while running on "haswell"). # If "true" only allow targets that are compatible with the host. host_compatible: true + # When "true" concretize root specs of environments together, so that each unique + # package in an environment corresponds to one concrete spec. This ensures + # environments can always be activated. When "false" perform concretization separately + # on each root spec, allowing different versions and variants of the same package in + # an environment. + unify: false \ No newline at end of file -- cgit v1.2.3-60-g2f50