-
Notifications
You must be signed in to change notification settings - Fork 5
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
Break down Bright modules namespace on per category depth level, for Lmod compatibility #4
Comments
@rtmclay :
|
I think that modulefile2 is mostly O.K. I think that there is a possible problem with acml/gcc-int64/64/5.3.1 and acml/gcc/64/5.3.1. According to the rules that we are proposing a user could load both acml/gcc-int64/... and acml/gcc. If that is O.K. then I guess things would be O.K. comments? |
Wouldn't "acml" be the conflicting part? If not, this issue would exist with all others, no? On Wednesday, 30 March 2016, Robert McLay notifications@github.com wrote:
echo "sysadmin know better bash than english"|sed s/min/mins/ |
@rtmclay : any news on supporting multiple categories, yet?! |
No ETA. I have started working on it but every time I start looking at it my head spins. It is basically a rewrite of Lmod from the ground up. Eventually, I'll be able to reuse part of the current implementation but until I'm farther along I can't give an ETA. I hope to have it done by the end of this year, but I'm not promising that. |
@rtmclay : |
since 7.x Lmod release things work as they should and there is no immediate need for category split; therefor I consider this case closed for now - to be reopened if reality proves need to do otherwise. |
as discussed, these should belong to distinct directories:
Then, the only expected change would be the output of the command
module avail
.fi. MODULEPATH would have 2 or 3 sections instead of one.
Everything else we expect it to work like before, without any changes at all.
Why we do this? Lmod would then be able to honor the one-name rule! (protects from conflicts)
The text was updated successfully, but these errors were encountered: