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?



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]

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

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