Dear Loris,
On 26/06/2019 10:47, Loris Bennett wrote:
Hi,
I am currently trying to implement a hook which will cause additional
variants of a piece of software to be built. However, my abortive
attempts have caused the current module to become unavailable for users;
'module av' shows the module, but 'module add' fails with
Lmod has detected the following error: The following module(s) are
unknown: "CP2K/6.1-intel-2018a"
Aside from having a separate test system, what is the canonical way of
separating such speculative builds from the production setup?
Usually you just instruct EasyBuild to install that software in a
separate directory, and then you use "module use" to make the modules
tool aware of them.
Something like:
$ eb --installpath /tmp/$USER foo-1.2.3.eb
$ module use /tmp/$USER/modules/all
$ module load foo/1.2.3
('module load' is equivalent to 'module add')
regards,
Kenneth
