From 63dca0c6ccf83b60e9aff3278c11869f8de5ebf5 Mon Sep 17 00:00:00 2001 From: Massimiliano Culpo Date: Wed, 28 Sep 2022 09:15:36 +0200 Subject: [PATCH] Remove mentions of "best-effort" matrix expansion in the docs (#32755) closes #20340 --- lib/spack/docs/environments.rst | 25 ------------------------- 1 file changed, 25 deletions(-) diff --git a/lib/spack/docs/environments.rst b/lib/spack/docs/environments.rst index 9be2ab4684..2b98137314 100644 --- a/lib/spack/docs/environments.rst +++ b/lib/spack/docs/environments.rst @@ -623,31 +623,6 @@ The following two Environment manifests are identical: Spec matrices can be used to install swaths of software across various toolchains. -The concretization logic for spec matrices differs slightly from the -rest of Spack. If a variant or dependency constraint from a matrix is -invalid, Spack will reject the constraint and try again without -it. For example, the following two Environment manifests will produce -the same specs: - -.. code-block:: yaml - - spack: - specs: - - matrix: - - [zlib, libelf, hdf5+mpi] - - [^mvapich2@2.2, ^openmpi@3.1.0] - - spack: - specs: - - zlib - - libelf - - hdf5+mpi ^mvapich2@2.2 - - hdf5+mpi ^openmpi@3.1.0 - -This allows one to create toolchains out of combinations of -constraints and apply them somewhat indiscriminately to packages, -without regard for the applicability of the constraint. - ^^^^^^^^^^^^^^^^^^^^ Spec List References ^^^^^^^^^^^^^^^^^^^^