hlrs-software-stack/spack
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Spack chain docs: config should go in upstreams.yaml (#11225)

Browse source 
#11152 added documentation for #8772 but some details were based on
an earlier implementation that had changed by the time #8772 was
merged. In particular, #11152 mentioned that upstream Spack instances
were configured in config.yaml, when in fact they should be placed in
a separate upstreams.yaml config file; this PR updates the
documentation accordingly.
This commit is contained in:
Peter Scheibel 2019-04-18 18:57:10 -07:00 committed by GitHub
parent 9cf650d2ab
commit 8a23154755
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
lib/spack/docs/chain.rst
View file

@ -11,11 +11,10 @@ Chaining Spack Installations
You can point your Spack installation to another installation to use any
packages that are installed there. To register the other Spack instance,
you can add it as an entry to ``config.yaml``:
you can add it as an entry to ``upstreams.yaml``:
.. code-block:: yaml
config:
upstreams:
spack-instance-1:
install_tree: /path/to/other/spack/opt/spack
@ -62,7 +61,7 @@ Using Multiple Upstream Spack Instances
A single Spack instance can use multiple upstream Spack installations. Spack
will search upstream instances in the order you list them in your
configuration. If your installation refers to instances X and Y, in that order,
then instance X must list Y as an upstream in its own ``config.yaml``.
then instance X must list Y as an upstream in its own ``upstreams.yaml``.
-----------------------------------
Using Modules for Upstream Packages
@ -80,7 +79,6 @@ configuration:
.. code-block:: yaml
config:
upstreams:
spack-instance-1:
install_tree: /path/to/other/spack/opt/spack