Skip to content

take EESSI_SITE_SOFTWARE_PREFIX into account, use site's Lmod RC file#4

Merged
casparvl merged 1 commit into
casparvl:update_site_package_behaviorfrom
bedroge:update_site_package_behavior
May 22, 2026
Merged

take EESSI_SITE_SOFTWARE_PREFIX into account, use site's Lmod RC file#4
casparvl merged 1 commit into
casparvl:update_site_package_behaviorfrom
bedroge:update_site_package_behavior

Conversation

@bedroge
Copy link
Copy Markdown

@bedroge bedroge commented May 22, 2026

No description provided.

@bedroge
Copy link
Copy Markdown
Author

bedroge commented May 22, 2026

Note that I don't check for the existence of the file: we don't do that in the module either, and Lmod doesn't seem to complain if you add a non-existing path to $LMOD_RC.

We do check for the existence of the EESSI lmodrc.lua file in this same file: https://github.com/EESSI/software-layer-scripts/blob/main/init/eessi_environment_variables#L104. But we don't do that in the module either.

@casparvl
Copy link
Copy Markdown
Owner

I think that's fine, we didn't do it for the default EESSI_SITE_SOFTWARE_PATH either. Adding a path to the MODULEPATH for which the dir doesn't exist is harmless.

@casparvl
Copy link
Copy Markdown
Owner

I think some of this should be quoted, but will do that myself.

@casparvl casparvl merged commit 7b44e69 into casparvl:update_site_package_behavior May 22, 2026
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.

2 participants