Skip to content

New modulecmd detection algorithm.#2426

Closed
skosukhin wants to merge 1 commit intospack:developfrom
skosukhin:pr_modulecmd
Closed

New modulecmd detection algorithm.#2426
skosukhin wants to merge 1 commit intospack:developfrom
skosukhin:pr_modulecmd

Conversation

@skosukhin
Copy link
Copy Markdown
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
Copy Markdown
Member

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

@skosukhin
Copy link
Copy Markdown
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.

2 participants