diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2022-05-23 22:20:34 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-23 13:20:34 -0700 |
| commit | f7258e246fdf836a69c3dfba403e42f780f679db (patch) | |
| tree | 19955ba43cdda30e6bb67ef1cd2bf5c077e38878 /lib/spack/docs/environments.rst | |
| parent | ff980a14522652d3c9ee94bb3318a4bda7680b6b (diff) | |
| download | spack-f7258e246fdf836a69c3dfba403e42f780f679db.tar.gz spack-f7258e246fdf836a69c3dfba403e42f780f679db.tar.bz2 spack-f7258e246fdf836a69c3dfba403e42f780f679db.tar.xz spack-f7258e246fdf836a69c3dfba403e42f780f679db.zip | |
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
Diffstat (limited to 'lib/spack/docs/environments.rst')
| -rw-r--r-- | lib/spack/docs/environments.rst | 17 |
1 files changed, 11 insertions, 6 deletions
diff --git a/lib/spack/docs/environments.rst b/lib/spack/docs/environments.rst index 7744dc87e6..fca70d8af9 100644 --- a/lib/spack/docs/environments.rst +++ b/lib/spack/docs/environments.rst @@ -281,8 +281,8 @@ need to be installed alongside each other. Central installations done at HPC centers by system administrators or user support groups are a common case that fits in this behavior. Environments *can also be configured to concretize all -the root specs in a self-consistent way* to ensure that -each package in the environment comes with a single configuration. This +the root specs in a unified way* to ensure that +each package in the environment corresponds to a single concrete spec. This mode of operation is usually what is required by software developers that want to deploy their development environment. @@ -499,7 +499,7 @@ Spec concretization Specs can be concretized separately or together, as already explained in :ref:`environments_concretization`. The behavior active -under any environment is determined by the ``concretization`` property: +under any environment is determined by the ``concretizer:unify`` property: .. code-block:: yaml @@ -509,10 +509,15 @@ under any environment is determined by the ``concretization`` property: - netcdf - nco - py-sphinx - concretization: together + concretizer: + unify: true -which can currently take either one of the two allowed values ``together`` or ``separately`` -(the default). +.. note:: + + The ``concretizer:unify`` config option was introduced in Spack 0.18 to + replace the ``concretization`` property. For reference, + ``concretization: separately`` is replaced by ``concretizer:unify:true``, + and ``concretization: together`` is replaced by ``concretizer:unify:false``. .. admonition:: Re-concretization of user specs |