-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
There are a few things that can be done to further improve the Lmod-based init scripts.
- Make the
bash,zshandkshinitialisation scripts POSIX compliant- This would also allow us to have a unique script with symlinks for the others (including a new
shvariant which should also work withdash). The only thing that is unique to each script is the name of the shell, since the script is (typically)sourced$0is the name of the current shell (with potentially a leading-). We need the shell to know what initialisation script to use from Lmod. It should be possible to store the shell as$(basename -- ${0#-})which will work for bothsourceand direct execution since the filename and shell are meant to be the same (and even better, for asourced script it will be forgiving even if you call the "wrong" script).dashwould need to be special-cased (dash->sh).
- This would also allow us to have a unique script with symlinks for the others (including a new
- Currently, if you follow the sequence
you end up with the "wrong" EESSI version loaded as
ocaisa@~$ source /cvmfs/software.eessi.io/versions/2025.06/init/lmod/bash Modules purged before initialising EESSI Module for EESSI/2025.06 loaded successfully EESSI has selected aarch64/neoverse_n1 as the compatible CPU target for EESSI/2025.06 EESSI did not identify an accelerator on the system (for debug information when loading the EESSI module, set the environment variable EESSI_MODULE_DEBUG_INIT) {EESSI/2025.06} ocaisa@~$ source /cvmfs/software.eessi.io/versions/2023.06/init/lmod/bash Running "module reset". Resetting modules to system default. The following $MODULEPATH directories have been removed: None Module for EESSI/2025.06 loaded successfully {EESSI/2025.06} ocaisa@~$EESSI_VERSIONwas set when you called the second script (which is an override variable). This needs to be special cased.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels