Update docs on usage of spack config vars in concrete env path
This commit is contained in:
parent
e56ffe3e8a
commit
5d9de68725
1 changed files with 4 additions and 2 deletions
|
@ -494,7 +494,9 @@ from the command line.
|
||||||
|
|
||||||
You can also include an environment directly in the ``spack.yaml`` file. It
|
You can also include an environment directly in the ``spack.yaml`` file. It
|
||||||
involves adding the ``include_concrete`` heading in the yaml followed by the
|
involves adding the ``include_concrete`` heading in the yaml followed by the
|
||||||
absolute path to the independent environments.
|
absolute path to the independent environments. Note, that you may use Spack
|
||||||
|
config variables such as ``$spack`` or environment variables as long as the
|
||||||
|
expression expands to an absolute path.
|
||||||
|
|
||||||
.. code-block:: yaml
|
.. code-block:: yaml
|
||||||
|
|
||||||
|
@ -504,7 +506,7 @@ absolute path to the independent environments.
|
||||||
unify: true
|
unify: true
|
||||||
include_concrete:
|
include_concrete:
|
||||||
- /absolute/path/to/environment1
|
- /absolute/path/to/environment1
|
||||||
- /absolute/path/to/environment2
|
- $spack/../path/to/environment2
|
||||||
|
|
||||||
|
|
||||||
Once the ``spack.yaml`` has been updated you must concretize the environment to
|
Once the ``spack.yaml`` has been updated you must concretize the environment to
|
||||||
|
|
Loading…
Reference in a new issue