zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove mentions of "best-effort" matrix expansion in the docs (#32755)

Browse Source 
closes #20340
This commit is contained in:
Massimiliano Culpo 2022-09-28 09:15:36 +02:00 committed by GitHub
parent 51feed16db
commit 63dca0c6cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
lib/spack/docs/environments.rst
View File

@ -623,31 +623,6 @@ The following two Environment manifests are identical:
Spec matrices can be used to install swaths of software across various Spec matrices can be used to install swaths of software across various
toolchains. 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 Spec List References
^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^