not very happy with this parameter name, since it's not clear this only covers part of the full module name (only the bit that is now covered by name)

maybe it should be name_in_module?

@rjeschmi, @wpoely86: suggestions?

It doesn't seem too bad. It is the "name" in the modulefile, so it is accurate.

we use 'module name' in different places to refer to the whole thing, I'd like to make it crystal clear this is not the 'full' module name, just the software name part of it...

modmetaname?

IE it is the metadata for the module

@rjeschmi: quoting you: "It is the "name" in the modulefile", so name_in_module is almost a one-to-one match?

'meta' is so... meta. ;-)

I don't like _ It also makes the option reorder somewhere else alphabetically.

modaltsoftname ?

modaltappname ?

I like modaltsoftname: descriptive and long enough so you'll think twice before using it. @rjeschmi?

Sounds good

On Tue, Sep 15, 2015, 3:53 PM Kenneth Hoste [email protected]
wrote:

In easybuild/framework/easyconfig/default.py
#1389 (comment)
:

 'modextrapaths': [{}, "Extra paths to be prepended in module file", MODULES],
 'modextravars': [{}, "Extra environment variables to be added to module file", MODULES],
 'modloadmsg': [{}, "Message that should be printed when generated module is loaded", MODULES],
 'modluafooter': ["", "Footer to include in generated module file (Lua syntax)", MODULES],

• 'modname': [None, "Module name to use (rather than using software name", MODULES],

I like modaltsoftname: descriptive and long enough so you'll think twice
before using it. @rjeschmi https://github.com/rjeschmi?

—
Reply to this email directly or view it on GitHub
https://github.com/hpcugent/easybuild-framework/pull/1389/files#r39556436
.