Then why not make 3.2.10 a required dependency instead? The option --strict=ignore could be used if that version is not available (“own responsibility”). But then again, the “module purge” issue should not cause the bootstrap to fail.
-- Thanks all, Franky Op 28-jan.-2014, om 06:08 heeft Fotis Georgatos <[email protected]> het volgende geschreven: > I am pondering on how to reduce future support effort. > > On Jan 27, 2014, at 10:27 PM, Kenneth Hoste wrote: >> I follow Jens in recommending you to update to v3.2.10, also because an >> important bug was fixed in that version w.r.t. a modulecmd segfault that >> only occurs with "large" module environments (e.g. the ones easily obtained >> with EasyBuild). > > I think that running EasyBuild with versions of env-modules <3.2.10 is > basically > looking for trouble, because those versions are known to contain bugs that > affect > you exactly in the domain where EasyBuild would excel (ie. using multiple > modules). > > In fact, I think someone should only be able to run EB with --strict=ignore > or such, > whenever the underlying modules technology is known to contain bugs. Would > you agree?
