Skip to content

docs: say what users set to load a target's site installs - #32

Merged
HaoZeke merged 1 commit into
mainfrom
fix/users-see-site-installs
Nov 17, 2026
Merged

HaoZeke merged 1 commit into
mainfrom
fix/users-see-site-installs

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

After a good nightly, users had no way to 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, and stopped there.

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.

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.
@HaoZeke
HaoZeke merged commit b209a0d into main Nov 17, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant