Skip to content
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

New modulecmd detection algorithm. #2426

Closed
wants to merge 1 commit into from

Conversation

skosukhin
Copy link
Member

Sometimes modulecmd is not in the PATH and the only way to find it is to parse the corresponding shell function. This is what this PR offers.

@mamelara
Copy link
Member

@skosukhin any reason why this was closed? It's pretty useful

@skosukhin
Copy link
Member Author

@mamelara I've closed this because we can't be sure that the executable called by the 'module' shell function is actually what we expect it to be. I've stumbled upon a very strange configuration of the Environment Modules where the 'module' shell function called not 'modulecmd' but some additional wrapping script, which acted differently. So, to make thing simple and straightforward I decided that it was much better just to let users know that they need to add 'modulecmd' executable to the PATH and it was up to them to make sure that it was the 'right' one.

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.

None yet

2 participants