Dear Alexei,

There is a long discussion about this use case in 
https://github.com/easybuilders/easybuild-framework/issues/2143 and how to do 
it.

In a hierarchical scheme you would have to rebuild any modules you have that 
extend the path setting (with EASYBUILD_SUBDIR_USER_MODULES set). You also need 
to tell EasyBuild to look in both module trees, I did this with an alias in a 
dedicated lua module:
set_alias("eb","env 
MODULEPATH=".."/path/to/global/module/tree/ending/in/modules/all"..':$MODULEPATH
 eb')

Kind regards,

Alan

On 12 October 2017 at 16:45, Alexi Rivera 
<[email protected]<mailto:[email protected]>> wrote:
Hello all,

We are looking into allowing users on our cluster to build modules with 
easybuild into their local directories.
However, it would be optimal if dependencies would be resolved against the 
global installationdirectory that we use.

That is, it seems that when installing to a new directory, you need to build 
all dependencies again in this tree.
I'm thinking it will take up alot of unnecessary space if every user needs to 
build every dependency separately.

Is there a way to achieve what we're looking for?

Best regards,
Alexi Rivera




--
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: [email protected]<mailto:[email protected]>
WWW:    http://www.fz-juelich.de/ias/jsc/EN


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to