From 2ab974f5301746f20ff19cb991951158a9c498fd Mon Sep 17 00:00:00 2001 From: Harmen Stoppels Date: Mon, 7 Nov 2022 15:38:24 +0100 Subject: concretizer:unify:true as a default (#31787) `spack env create` enables a view by default (in a weird hidden directory, but well...). This is asking for trouble with the other default of `concretizer:unify:false`, since having different flavors of the same spec in an environment, leads to collision errors when generating the view. A change of defaults would improve user experience: However, `unify:true` makes most sense, since any time the issue is brought up in Slack, the user changes the concretization config, since it wasn't the intention to have different flavors of the same spec, and install times are decreased. Further we improve the docs and drop the duplicate root spec limitation --- etc/spack/defaults/concretizer.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'etc') diff --git a/etc/spack/defaults/concretizer.yaml b/etc/spack/defaults/concretizer.yaml index 7311354c28..f455aa723d 100644 --- a/etc/spack/defaults/concretizer.yaml +++ b/etc/spack/defaults/concretizer.yaml @@ -33,4 +33,4 @@ concretizer: # 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 + unify: true \ No newline at end of file -- cgit v1.2.3-60-g2f50