New SPACK_BASE environment variable in Spack module #42
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.
While updating the documentation, Arno spotted that the given path to the ARCHER2 package repos didn't work. Using
SPACK_ROOT, it would have neededbecause
SPACK_ROOTrefers to the Spack installation itself, rather than our clone ofarcher2-spackwhich contains it.I've fixed the module on ARCHER2 and the documentation to instead use a new environment variable
SPACK_BASEwhich refers not to Spack itself but to thatarcher2-spacklocation, so users can now use the nicerIf we ever need to work outside Lmod with anything else not in Spack itself but in our own configs, this also makes it that tiny bit easier to access it.
This PR makes the same change in the template modulefile, so any time that we automatically generate the modulefile from now on it will include the change to set
SPACK_BASE.