Hi Olaf,
On 13/03/14 13:31, Olaf Walter wrote:
Hi Kenneth,
is there a way to make --modules-footer work per-package?
The only way I could image is to call eb for this one package with the
--modules-footer, right?
Yes, or only set $EASYBUILD_MODULES_FOOTER in the session where you're
building that package.
The modules-footer option is intended to be used in a general sense,
e.g. by defining modules-footer in an EasyBuild config file, but nothing
is stopping you from using it only once, of course.
We will look into supporting ways of making software-specific site
customizations (possibly only for easyconfig in the new format), but
we're not there yet.
regards,
Kenneth
Olaf
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]]
Im Auftrag von Kenneth Hoste
Gesendet: Donnerstag, 13. März 2014 13:05
An: [email protected]
Betreff: Re: [easybuild] custom conflicts
Hi Olaf,
On 13/03/14 11:01, Fotis Georgatos wrote:
Hi Olaf,
On Mar 13, 2014, at 10:53 AM, Olaf Walter wrote:
In this case, I would have to make sure that MapSplice and bowtie are not loaded at the
same time. How can I add this "custom conflict" line to the generated modules
file?
I'd suggest to see that treated as one more instance of:
https://github.com/hpcugent/easybuild-framework/issues/860
(ie. implement mpi-stack conflict in the style of Lmod's "family" feature)
Then, `family = ['bowtie']` should do the trick.
If you agree with the above, add +1 in the relevant issue describing the
use-case.
To be clear: the family thing is not supported yet, it's a proposed feature.
What should already work is the support for adding a custom footer to
the generated modules, see the command line option --modules-footer .
You can provide a file that contains something like "conflict Boost",
which will be added to the generated module file.
Let us know if that approach works out.
regards,
Kenneth
