-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
only use environment variable to find module command binary if command can't be found in $PATH #1275
Conversation
…d can't be found in $PATH
Refer to this link for build results (access rights to CI server needed): |
@@ -122,7 +122,7 @@ class ModulesTool(object): | |||
TERSE_OPTION = (0, '--terse') | |||
# module command to use | |||
COMMAND = None | |||
# environment variable to determine the module command (instead of COMMAND) | |||
# environment variable that may refer to module command |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing documentation how it resolves it now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs update at easybuilders/easybuild#119
…LMOD_CMD are different
Refer to this link for build results (access rights to CI server needed): |
…ia $PATH, enhance test_lmod_specific unit test
Refer to this link for build results (access rights to CI server needed): |
Thanks for the review @stdweird! |
only use environment variable to find module command binary if command can't be found in $PATH
only use environment variable to find module command binary if command can't be found in $PATH
If
lmod
is found in$PATH
, we shouldn't be using the value of$LMOD_CMD
to determine the path tolmod
.When Lmod is available both on the system and in the user's account, we may end up using the wrong
lmod
binary that way (cfr. Taito @ CSC.fi).