Allow use of alternate envvar(s) to $HOME for user modules#3558
Allow use of alternate envvar(s) to $HOME for user modules#3558boegel merged 21 commits intoeasybuilders:developfrom
Conversation
|
@boegel This is also interesting for EESSI since it would allow sites to easily configure a stack built on top of the EESSI baseline |
|
Ha, nice. I have had vague thoughts in this direction a few weeks ago... |
boegel
left a comment
There was a problem hiding this comment.
@ocaisa It would be nice to have a more complete test for this, where the generated module file actually gets loaded, and the effect on the changes in the environment are checked.
That may be a significant additional effort though...
Co-authored-by: Kenneth Hoste <[email protected]>
…mework into alt-envvar-user-mod
|
|
|
@akesandgren Can you take a look at this to see if it makes sense for you too? We kind of need this so that we can create additional installations shared among a project as opposed to (or as well as) just for a single user. |
…d to add to MODULEPATH
… to ensure (mainly Tcl) syntax is correct
…sing Lmod as modules tool
The use of
$HOMEfor user modules is quite restrictive, it makes it very difficult to share user space installations. Even if we use a symlink to an accessible space it is still problematic as therootdirectory is still placed into the module (with $HOME expanded).The nice thing about
$HOMEis that it is guaranteed to exist and right now that is required by module file that we create. Nevertheless, if a site is willing to take on using another (configurable) variable instead (with a sensible default value, such as$HOME), it would make user space installations with a module hierarchy a lot more flexible.