Add documentation for chaining Spack instances #11152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…installed locally and upstream, and usage of upstream external packages
michaelkuhn
reviewed
Apr 10, 2019
|
|
||
| There are two requirements to use the modules created by an upstream Spack | ||
| instance: firstly the upstream instance must do a ``spack module tcl refresh``, | ||
| which generates an index file that maps installed packages to their modules; |
There was a problem hiding this comment.
This is probably unrelated to this PR but would it not make more sense to generate/update the index whenever a module is generated instead of forcing users to refresh them?
There was a problem hiding this comment.
It would. I suppose I originally didn't want to do the extra work in a Spack instance if it wasn't being used as an upstream, but it's not a lot of work.
|
It might be worth adding a note that SPACK settings like compiler.yaml or packages.yaml are not inherited from the upstream but only the packages installed by upstream. Thus, users may need to add compilers again fist and they willnot (automatically) get special settings for e.g. openmpi defined in the sysadmin's SPACK instance. |
scheibelp
added a commit
that referenced
this pull request
Apr 19, 2019
#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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates https://spack.readthedocs.io/en/latest/ to add documentation on the feature added in #8772, which allows a Spack instance to point to another Spack instance to use the packages installed there.