Repository navigation
docs: say what users set to load a target's site installs - #32
Merged
Merged
Conversation
After a good nightly, no user could load what it installed. The EESSI module puts a site install on MODULEPATH only where EESSI_SITE_SOFTWARE_PREFIX is set before it loads, and adds the tree of the CPU target it selected, while run builds for cpu_target. The pages said where EESSI-extend installs, not either of these. A how-to guide now names the variable and value users need, says that cpu_target has to be the target users' jobs load, which with eessi-arch-guard as the TaskProlog is the one the guard selects, and how to see it, and that a job keeps the prefix of the shell that submitted it. Its site file and docs/examples/site-installs.sh give the output it shows, and the README lists it. The test ties the guide to the prefix and target that explain shows for each target of its site file.
This file contains hidden or 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
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.
After a good nightly, users had no way to load what it installed. The EESSI module puts a site install on
MODULEPATHonly whereEESSI_SITE_SOFTWARE_PREFIXis set before it loads, and adds the tree of the CPU target it selected, whilerunbuilds forcpu_target. The pages said where EESSI-extend installs, and stopped there.A how-to guide now names the variable and value users need, says that
cpu_targethas to be the target users' jobs load, which with eessi-arch-guard as theTaskPrologis the one the guard selects, and how to see it, and that a job keeps the prefix of the shell that submitted it. Its site file anddocs/examples/site-installs.shgive the output it shows, and the README lists it. The test ties the guide to the prefix and target thatexplainshows for each target of its site file.