Hi Adam, On 25 Sep 2013, at 18:37, Adam DeConinck wrote:
> Hi Kenneth, > >> If all goes well, EasyBuild v1.8.0 should include support for custom module >> naming schemes [1], which we consider to be a major feature, >> that should allow new adopters to more fluently make the transition to >> EasyBuild. > > Exciting! I see this being very helpful. > > If I understand correctly from the PR, each new naming scheme will be > implemented as a Python module which takes things like the module name, > version, and toolchain and outputs a name. The module should contain a function that takes a parsed easyconfig (basically a dictionary), and spits out the module name as a string (see also [3]). > Will the 1.8 release provide > any examples of how to build these schemes -- either as built-in > alternatives to the default, or in the docs? We will ship the EasyBuild default module naming scheme (+ a stupid test module naming scheme) [1,2], and have some documentation ready which includes another example [3]. It's still a bit involved and restricted now, but that will drastically improve once https://github.com/hpcugent/easybuild-framework/issues/687 is tackled (but probably not for EB v1.8). If you play around with this, let us know if something is not clear, or if it's not working as expected. [1] https://github.com/hpcugent/easybuild-framework/blob/develop/easybuild/tools/module_naming_scheme/easybuild_module_naming_scheme.py [2] https://github.com/hpcugent/easybuild-framework/blob/develop/test/framework/sandbox/easybuild/tools/module_naming_scheme/test_module_naming_scheme.py [3] https://github.com/hpcugent/easybuild/wiki/Using-a-custom-module-naming-scheme regards, Kenneth
