From b9816a97fc992c2a4171e0573ec5ba8f06fefc93 Mon Sep 17 00:00:00 2001 From: mSamiolo Date: Thu, 23 May 2024 00:04:53 +0200 Subject: docs: update chain.rst to improve discussion of upstreams (#43918) * Update chain.rst * Update lib/spack/docs/chain.rst Co-authored-by: Wouter Deconinck * Update lib/spack/docs/chain.rst Co-authored-by: Wouter Deconinck * docs: rm leading spaces to avoid indent --------- Co-authored-by: Wouter Deconinck --- lib/spack/docs/chain.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/spack/docs/chain.rst b/lib/spack/docs/chain.rst index e4a275df66..bd0241c8bb 100644 --- a/lib/spack/docs/chain.rst +++ b/lib/spack/docs/chain.rst @@ -11,7 +11,8 @@ 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 ``upstreams.yaml``: +you can add it as an entry to ``upstreams.yaml`` at any of the +:ref:`configuration-scopes`: .. code-block:: yaml @@ -22,7 +23,8 @@ you can add it as an entry to ``upstreams.yaml``: install_tree: /path/to/another/spack/opt/spack ``install_tree`` must point to the ``opt/spack`` directory inside of the -Spack base directory. +Spack base directory, or the location of the ``install_tree`` defined +in :ref:`config.yaml `. Once the upstream Spack instance has been added, ``spack find`` will automatically check the upstream instance when querying installed packages, -- cgit v1.2.3-70-g09d2