Hi Bart, On Apr 23, 2014, at 6:13 AM, Bart Verleye wrote > all bio cae chem compiler data devel lang lib math mpi numlib > phys system toolchain tools vis > > I can understand the division 'software compilers libs mpi', however, I don't > see the point of having the others. We had some discussions about this here > at our centre, but I didn't really hear a convincing argument yet.
Since I've been pushing much of the related activity, let me explain: - First, yes, we had plenty of the non-convincing argument rounds already :) - In my own eyes, it is more of a beauty contest, than exact science. - We agree that categorization may need be customized on per-site basis - Current moduleclasses are merely 1 instance, initially influenced by HLRS - At some point we would to allow multi-value (ie. belong to 2 or more classes) - Searching is known to be tricky; except for when Lmod searches on path itself! I've seen users busy around this last statement and I am convinced that the current layout is not too bad, just requires some extra care & love. (any offers? :) references: * https://github.com/hpcugent/easybuild-framework/pull/525 * https://github.com/hpcugent/easybuild-framework/issues/209 In your case, you want to split'em in 4 categories, so it is piece of cake, really: Simply pass with a sed-expression all easyconfigs and blindly modify anything not in ['compilers', 'libs', 'mpi'] towards 'software'. Or, use --try-amend=moduleclass=software, selectively where you need to. The more pythonic way to do it, would be perhaps to allow for "category renaming" inside EB, and supply that as configuration information. That would allow arbitrary freedom to customize category names, on the assumption that you have well-defined N-to-1 mappings. best, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # Yelling in a CERN forum
