Hi Ben,

On 19/11/15 19:12, McGough, Benjamin E wrote:
In order to reduce complexity and provide users with a simple experience, I 
would like to hide all dependencies and toolchains built with easybuild.

Does this make sense?

I'm not sure entirely sure whether it does...

The problem is that the install directory is not hidden (i.e., doesn't start with a '.'), only the module file is.

So, if you want to have bzip v1.0.6 available as a module, and you're using it as a dependency somewhere that you want to hide, you'll probably end up reinstalling it the 2nd time (since the module isn't there yet, but the install directory is the same). I need to double-check on that though...

That is, unless you're building it as a hidden dependency *first*, and then use eb --module-only to also install it non-hidden.

During writing this, I think this is a bug, that we somehow need to deal with... Not entirely sure how though...


The full list of loaded modules is in the user's environment (we use 
Environment Modules, not Lmod yet), so we can extract the full module list 
(with hidden modules) if needed.

The problem I run into is that '--hide-deps' doesn't seem to go more than one 
dependency level down. For example, I am trying to build intel-2015b.eb, and if 
I specify all the dependencies in '--hide-deps=' it will hide icc, ifort, impi, 
and imkl but not iccifort or iimpi, which are listed as toolchains for impi and 
imkl.

Is there a way to build this toolchain hidden, without building the underlying 
toolchains separately?

That's just because --hide-deps does not apply to toolchains. I guess we could extend it such that you can do that too.

I'm not sure whether we should go with a --hide-toolchains here, or just allow to list toolchains in --hide-deps.

Any preference anyone?

What about a '--hide-all-deps' option?
I wouldn't create a separate configuration option for it (we have enough as is), but extending --hide-deps to support regular expressions makes sense.
Then you can basically use --hide-deps='.*'.

Would that work for you?

And finally: how good is your Python & git fu? Are you willing to take a stab at this yourself?

In any case: please open a feature request for this via https://github.com/hpcugent/easybuild-framework/issues .


regards,

Kenneth

Reply via email to