Re: [easybuild] Find hidden modules by default

2016-08-04 Thread Kenneth Hoste 

Hi Davide,

On 04/08/16 15:31, Vanzo, Davide wrote:
Thank you guys for your replies. I'm happy to see I'm not the only one 
that would benefit from this.


I totally agree with Kenneth on how this should be implemented. Am I 
wrong to assume that a positive side effect of this approach is to 
make the "hiddendependencies" option for easyconfig files redundant 
since EB will automatically look for hidden dependencies if no visible 
ones are found for the ones listed in "dependencies" and 
"builddependencies"?


Yes, that would probably make 'hiddendependencies' mostly redundant, but 
not entirely...


Using 'hiddendependencies' means that those dependencies will always be 
hidden, regardless of the EasyBuild configuration being used.


When we make the robot also consider hidden modules, this will be 
configurable (and probably enabled by default in EasyBuild v3.0 which 
should materialize later this year).


So, depending on your use case, 'hiddendependencies' may still be 
useful, e.g. when you want to hide dependencies for something in 
particular, but not as a general approach.



regards,

Kenneth



DV

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

On Aug 4 2016, at 5:11 am, Kenneth Hoste  wrote:

Hi Markus,

On 04/08/16 10:31, Markus Geimer wrote:
> All,
>
> It seems that with [2] in place, the dependency resolution already
> does "the right thing" as it parses the easyconfig files. But that
> obviously only works if the easyconfig contains the 'hidden'
> parameter. That said, maybe it is sufficient to ensure writing the
> 'hidden' info (wherever it comes from: 'hidden' flag, 'hide-deps',
> '--hidden' command-line option, ...) to the archived easyconfig?
> Or am I missing something?
That's probably only a partial solution, since you have no guarantee
that the archived easyconfig will be picked up the next time the same
installation is needed (the path to the archived easyconfigs is
not in
the robot path, by default).

I *think* that making the robot consider also hidden modules is as
simple as updating the 'find_resolved_modules' function to optionally
check also whether the module is available as hidden (which involves
tweaking the dep_mod_name to inject a '.', or something like that).

You may need to make a similar change to make dry-run spit out the
correct info though, which probably means some refactoring to ensure
that both the robot and dry-run use the same function to check
whether a
module is available or not...


regards,

Kenneth

>
> Markus
>
>
> [2] https://github.com/hpcugent/easybuild-framework/pull/1837
>
> On 08/04/16 08:58, Markus Geimer wrote:
>> Davide,
>>
>>> The most logical way of doing so seems to be by creating hidden
>>> modules for the dependencies we don't want the users to see.
However,
>>> when installing other easyconfig packages from the default
easyconfig
>>> files they cannot see the hidden modules and try to install
them again.
>>> Is there a way to tell EB to automatically look for hidden
packages
>>> without modifying the easyconfig files?
>> At this point not, unfortunately. A corresponding issue has
>> been created already quite some time ago [1], but since then
>> hasn't received much attention. Since I'm very interested in
>> this feature as well and would like to see it implemented
>> rather sooner than later, I recently started looking into it.
>> But I'm still far from a clean and working solution -- though
>> Kenneth claims that it shouldn't be too hard... But that's
>> what he is saying all the time ;-)
>>
>> Markus
>>
>>
>> [1] https://github.com/hpcugent/easybuild-framework/issues/1079
>
> --
> Dr. Markus Geimer
> Juelich Supercomputing Centre
> Institute for Advanced Simulation
> Forschungszentrum Juelich GmbH
> 52425 Juelich, Germany
>
> Phone: +49-2461-61-1773
> Fax: +49-2461-61-6656
> E-mail: m.gei...@fz-juelich.de
> WWW: http://www.fz-juelich.de/jsc/
>
>
>
>


>


> 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),

Re: [easybuild] Find hidden modules by default

2016-08-04 Thread Vanzo, Davide 
Thank you guys for your replies. I'm happy to see I'm not the only one that 
would benefit from this.

I totally agree with Kenneth on how this should be implemented. Am I wrong to 
assume that a positive side effect of this approach is to make the 
"hiddendependencies" option for easyconfig files redundant since EB will 
automatically look for hidden dependencies if no visible ones are found for the 
ones listed in "dependencies" and "builddependencies"?

DV

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

On Aug 4 2016, at 5:11 am, Kenneth Hoste  wrote:

Hi Markus,

On 04/08/16 10:31, Markus Geimer wrote:
> All,
>
> It seems that with [2] in place, the dependency resolution already
> does "the right thing" as it parses the easyconfig files. But that
> obviously only works if the easyconfig contains the 'hidden'
> parameter. That said, maybe it is sufficient to ensure writing the
> 'hidden' info (wherever it comes from: 'hidden' flag, 'hide-deps',
> '--hidden' command-line option, ...) to the archived easyconfig?
> Or am I missing something?
That's probably only a partial solution, since you have no guarantee
that the archived easyconfig will be picked up the next time the same
installation is needed (the path to the archived easyconfigs is not in
the robot path, by default).

I *think* that making the robot consider also hidden modules is as
simple as updating the 'find_resolved_modules' function to optionally
check also whether the module is available as hidden (which involves
tweaking the dep_mod_name to inject a '.', or something like that).

You may need to make a similar change to make dry-run spit out the
correct info though, which probably means some refactoring to ensure
that both the robot and dry-run use the same function to check whether a
module is available or not...

regards,

Kenneth

>
> Markus
>
>
> [2] https://github.com/hpcugent/easybuild-framework/pull/1837
>
> On 08/04/16 08:58, Markus Geimer wrote:
>> Davide,
>>
>>> The most logical way of doing so seems to be by creating hidden
>>> modules for the dependencies we don't want the users to see. However,
>>> when installing other easyconfig packages from the default easyconfig
>>> files they cannot see the hidden modules and try to install them again.
>>> Is there a way to tell EB to automatically look for hidden packages
>>> without modifying the easyconfig files?
>> At this point not, unfortunately. A corresponding issue has
>> been created already quite some time ago [1], but since then
>> hasn't received much attention. Since I'm very interested in
>> this feature as well and would like to see it implemented
>> rather sooner than later, I recently started looking into it.
>> But I'm still far from a clean and working solution -- though
>> Kenneth claims that it shouldn't be too hard... But that's
>> what he is saying all the time ;-)
>>
>> Markus
>>
>>
>> [1] https://github.com/hpcugent/easybuild-framework/issues/1079
>
> --
> Dr. Markus Geimer
> Juelich Supercomputing Centre
> Institute for Advanced Simulation
> Forschungszentrum Juelich GmbH
> 52425 Juelich, Germany
>
> Phone: +49-2461-61-1773
> Fax: +49-2461-61-6656
> E-mail: m.gei...@fz-juelich.de
> WWW: http://www.fz-juelich.de/jsc/
>
>
>
> 
> 
> 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
> 
> 
>

Re: [easybuild] Cannot compile RELION with EasyBuild 2.8

2016-08-04 Thread Kenneth Hoste 



On 04/08/16 11:14, Alan O'Cais wrote:

I've opended a PR that should (might?) fix the problem:
https://github.com/hpcugent/easybuild-framework/pull/1862


I merged this, but shortly after realized that this doesn't fix the 
problem at all, since this only deals with the dependencies of a 
toolchain itself (i.e. the toolchain components).


Alan's proposed change did point me in the right direction though: I 
reproduced the problem in a test, and implemented a fix in 
https://github.com/hpcugent/easybuild-framework/pull/1863 .



regards,

Kenneth


On 4 August 2016 at 10:59, Alan O'Cais > wrote:


I think the culprit is here:

https://github.com/hpcugent/easybuild-framework/blob/f00e82540a558f675f3019b0cc42415eb193a96d/easybuild/framework/easyconfig/easyconfig.py#L170



We don't take filtered deps into account here and go searching for
them.

On 3 August 2016 at 16:08, Kenneth Hoste > wrote:

Hi Riccardo,

On 18/07/16 15:32, Riccardo Murri wrote:

Hello,

as I'm trying to compile RELION with EB, I get an "unresolved
dependency" error for a dependency that's been filtered out::

 $ eb --filter-deps=libX11

/apps/easybuild/ebfiles/r/RELION/RELION-1.4-foss-2015a-singleprecision.eb
 [...]
 ERROR: Failed to process easyconfig

/apps/easybuild/ebfiles/r/RELION/RELION-1.4-foss-2015a-singleprecision.eb:
No easyconfig for {'external_module_metadata': {},
'full_mod_name': None, 'toolchain': {'version': '2015a',
'name': 'foss'}, 'name': 'libX11', 'dummy': False,
'short_mod_name': None, 'external_module': False,
'versionsuffix': '-Python-2.7.8', 'version': '1.6.3',
'toolchain_inherited': True, 'hidden': False,
'build_only': False} that matches toolchain hierarchy
generated by {'version': '2015a', 'name': 'foss'}

Why isn't `--filter-deps` honored here?

I have tried both EB 2.8.0 and 2.8.2 FWIW.


Hmm, that's weird...

It looks like this has something to do with
--minimal-toolchains being enabled, is that right?

Do you mind sharing both the easyconfig file you're using, and
the output of "eb --show-config"?


regards,

Kenneth




-- 
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: a.oc...@fz-juelich.de 
WWW: http://www.fz-juelich.de/ias/jsc/EN





--
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: a.oc...@fz-juelich.de 
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

Re: [easybuild] Find hidden modules by default

2016-08-04 Thread Kenneth Hoste 

Hi Markus,

On 04/08/16 10:31, Markus Geimer wrote:

All,

It seems that with [2] in place, the dependency resolution already
does "the right thing" as it parses the easyconfig files.  But that
obviously only works if the easyconfig contains the 'hidden'
parameter.  That said, maybe it is sufficient to ensure writing the
'hidden' info (wherever it comes from: 'hidden' flag, 'hide-deps',
'--hidden' command-line option, ...) to the archived easyconfig?
Or am I missing something?
That's probably only a partial solution, since you have no guarantee 
that the archived easyconfig will be picked up the next time the same 
installation is needed (the path to the archived easyconfigs is not in 
the robot path, by default).


I *think* that making the robot consider also hidden modules is as 
simple as updating the 'find_resolved_modules' function to optionally 
check also whether the module is available as hidden (which involves 
tweaking the dep_mod_name to inject a '.', or something like that).


You may need to make a similar change to make dry-run spit out the 
correct info though, which probably means some refactoring to ensure 
that both the robot and dry-run use the same function to check whether a 
module is available or not...



regards,

Kenneth



Markus


[2] https://github.com/hpcugent/easybuild-framework/pull/1837

On 08/04/16 08:58, Markus Geimer wrote:

Davide,


The most logical way of doing so seems to be by creating hidden
modules for the dependencies we don't want the users to see. However,
when installing other easyconfig packages from the default easyconfig
files they cannot see the hidden modules and try to install them again.
Is there a way to tell EB to automatically look for hidden packages
without modifying the easyconfig files?

At this point not, unfortunately.  A corresponding issue has
been created already quite some time ago [1], but since then
hasn't received much attention.  Since I'm very interested in
this feature as well and would like to see it implemented
rather sooner than later, I recently started looking into it.
But I'm still far from a clean and working solution -- though
Kenneth claims that it shouldn't be too hard...  But that's
what he is saying all the time ;-)

Markus


[1] https://github.com/hpcugent/easybuild-framework/issues/1079


--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone:  +49-2461-61-1773
Fax:+49-2461-61-6656
E-mail: m.gei...@fz-juelich.de
WWW:http://www.fz-juelich.de/jsc/





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

Re: [easybuild] Find hidden modules by default

2016-08-04 Thread Markus Geimer 
The downside is that this is an "all or nothing" approach.  For
example, you may want to hide the M4/flex/Bison on the dummy
level used for bootstrapping, but expose the same packages on
the GCCcore level.  No way to do this with 'hide-deps', AFAIK...

Markus


On 08/04/16 10:27, Alvarez, Damian wrote:
> Well, alternatively you can add the dependencies to
> EASYBUILD_HIDE_DEPS and have something like
> EASYBUILD_HIDE_DEPS="ANTLR,ATK,Autoconf,Automake,Bison,etc”, and
> those dependencies will be always hidden (so don’t install them
> directly, or do it with --hidden). If the version number and the
> suffix of your installed hidden dependencies match the dependencies
> of the easyconfigs you want to install then it will work just fine.
>
> Damian
>
> On 04/08/16 08:58, "easybuild-requ...@lists.ugent.be on behalf of Markus 
> Geimer"  m.gei...@fz-juelich.de> wrote:
>
> Davide,
>
> > The most logical way of doing so seems to be by creating hidden
> > modules for the dependencies we don't want the users to see. However,
> > when installing other easyconfig packages from the default easyconfig
> > files they cannot see the hidden modules and try to install them again.
> > Is there a way to tell EB to automatically look for hidden packages
> > without modifying the easyconfig files?
>
> At this point not, unfortunately.  A corresponding issue has
> been created already quite some time ago [1], but since then
> hasn't received much attention.  Since I'm very interested in
> this feature as well and would like to see it implemented
> rather sooner than later, I recently started looking into it.
> But I'm still far from a clean and working solution -- though
> Kenneth claims that it shouldn't be too hard...  But that's
> what he is saying all the time ;-)
>
> Markus
>
>
> [1] https://github.com/hpcugent/easybuild-framework/issues/1079
>
>


--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone:  +49-2461-61-1773
Fax:+49-2461-61-6656
E-mail: m.gei...@fz-juelich.de
WWW:http://www.fz-juelich.de/jsc/





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

Re: [easybuild] Cannot compile RELION with EasyBuild 2.8

2016-08-04 Thread Alan O'Cais 
I think the culprit is here:
https://github.com/hpcugent/easybuild-framework/blob/f00e82540a558f675f3019b0cc42415eb193a96d/easybuild/framework/easyconfig/easyconfig.py#L170

We don't take filtered deps into account here and go searching for them.

On 3 August 2016 at 16:08, Kenneth Hoste 
> wrote:
Hi Riccardo,

On 18/07/16 15:32, Riccardo Murri wrote:
Hello,

as I'm trying to compile RELION with EB, I get an "unresolved
dependency" error for a dependency that's been filtered out::

 $ eb --filter-deps=libX11 
/apps/easybuild/ebfiles/r/RELION/RELION-1.4-foss-2015a-singleprecision.eb
 [...]
 ERROR: Failed to process easyconfig 
/apps/easybuild/ebfiles/r/RELION/RELION-1.4-foss-2015a-singleprecision.eb: No 
easyconfig for {'external_module_metadata': {}, 'full_mod_name': None, 
'toolchain': {'version': '2015a', 'name': 'foss'}, 'name': 'libX11', 'dummy': 
False, 'short_mod_name': None, 'external_module': False, 'versionsuffix': 
'-Python-2.7.8', 'version': '1.6.3', 'toolchain_inherited': True, 'hidden': 
False, 'build_only': False} that matches toolchain hierarchy generated by 
{'version': '2015a', 'name': 'foss'}

Why isn't `--filter-deps` honored here?

I have tried both EB 2.8.0 and 2.8.2 FWIW.


Hmm, that's weird...

It looks like this has something to do with --minimal-toolchains being enabled, 
is that right?

Do you mind sharing both the easyconfig file you're using, and the output of 
"eb --show-config"?


regards,

Kenneth



--
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: a.oc...@fz-juelich.de
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

Re: [easybuild] Find hidden modules by default

2016-08-04 Thread Alvarez, Damian 
Well, alternatively you can add the dependencies to EASYBUILD_HIDE_DEPS and 
have something like 
EASYBUILD_HIDE_DEPS="ANTLR,ATK,Autoconf,Automake,Bison,etc”, and those 
dependencies will be always hidden (so don’t install them directly, or do it 
with --hidden). If the version number and the suffix of your installed hidden 
dependencies match the dependencies of the easyconfigs you want to install then 
it will work just fine.

Damian

On 04/08/16 08:58, "easybuild-requ...@lists.ugent.be on behalf of Markus 
Geimer"  
wrote:

Davide,

> The most logical way of doing so seems to be by creating hidden
> modules for the dependencies we don't want the users to see. However,
> when installing other easyconfig packages from the default easyconfig
> files they cannot see the hidden modules and try to install them again.
> Is there a way to tell EB to automatically look for hidden packages
> without modifying the easyconfig files?

At this point not, unfortunately.  A corresponding issue has
been created already quite some time ago [1], but since then
hasn't received much attention.  Since I'm very interested in
this feature as well and would like to see it implemented
rather sooner than later, I recently started looking into it.
But I'm still far from a clean and working solution -- though
Kenneth claims that it shouldn't be too hard...  But that's
what he is saying all the time ;-)

Markus


[1] https://github.com/hpcugent/easybuild-framework/issues/1079


--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone:  +49-2461-61-1773
Fax:+49-2461-61-6656
E-mail: m.gei...@fz-juelich.de
WWW:http://www.fz-juelich.de/jsc/







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

Re: [easybuild] Find hidden modules by default

2016-08-04 Thread Markus Geimer 
Davide,

> The most logical way of doing so seems to be by creating hidden
> modules for the dependencies we don't want the users to see. However,
> when installing other easyconfig packages from the default easyconfig
> files they cannot see the hidden modules and try to install them again.
> Is there a way to tell EB to automatically look for hidden packages
> without modifying the easyconfig files?

At this point not, unfortunately.  A corresponding issue has
been created already quite some time ago [1], but since then
hasn't received much attention.  Since I'm very interested in
this feature as well and would like to see it implemented
rather sooner than later, I recently started looking into it.
But I'm still far from a clean and working solution -- though
Kenneth claims that it shouldn't be too hard...  But that's
what he is saying all the time ;-)

Markus


[1] https://github.com/hpcugent/easybuild-framework/issues/1079


--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone:  +49-2461-61-1773
Fax:+49-2461-61-6656
E-mail: m.gei...@fz-juelich.de
WWW:http://www.fz-juelich.de/jsc/





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

[easybuild] Find hidden modules by default

2016-08-04 Thread Vanzo, Davide 
Hello easybuilders,
I am testing EB + Lmod with hierarchical naming and I am trying to reconcile 
the huge amount of modules generated by EB with the need of reducing users' 
confusion by showing only the strictly necessary modules. The most logical way 
of doing so seems to be by creating hidden modules for the dependencies we 
don't want the users to see. However, when installing other easyconfig packages 
from the default easyconfig files they cannot see the hidden modules and try to 
install them again. Is there a way to tell EB to automatically look for hidden 
packages without modifying the easyconfig files?

Thank you

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

[easybuild] Hidden modules

2016-08-04 Thread Vanzo, Davide 
Hello easybuilders,
I am testing EB + Lmod with hierarchical naming and I am trying to reconcile 
the huge amount of modules generated by EB with the need of reducing users' 
confusion by showing only the strictly necessary modules. The most logical way 
of doing so seems to be by creating hidden modules for the dependencies we 
don't want the users to see. However, when installing other easyconfig packages 
from the default easyconfig files they cannot see the hidden modules and try to 
install them again. Is there a way to tell EB to automatically look for hidden 
packages without modifying the easyconfig files?

Thank you

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu