-
Notifications
You must be signed in to change notification settings - Fork 218
support for hierarchical module naming schemes #953
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
support for hierarchical module naming schemes #953
Conversation
…od, to make it always work with custom module naming schemes
…ming scheme by extending API for custom module naming schemes
… to $MODULEPATH, and generate prepend-paths statements in the module file for them
…them for non-dummy toolchains
…hierarchical scheme works; create correct paths in software/modules prefix
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.
commented out?
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.
yeah, should simply be removed
… error message cleaner)
…ule, use definition method in Toolchain class
|
@stdweird: remarks fixed! |
easybuild/framework/easyblock.py
Outdated
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.
is it part of the API? otehrwise, get rid of it
… nasty bits in options.py
|
remarks fixed (AGAIN :P)! |
|
@boegel looks fine to me now |
|
Jenkins: test this please |
support for hierarchical module naming schemes
@geimer: this should fix the problem that's blocking you right now
I might need to figure out one more thing w.r.t. the devel module name before this really works for you, I'm looking into that...