Hi Alan, Many thanks for the clarification, it helped a lot.
The EB hook injecting categories into lmod would be really great thing to have. Sorry, if I might have overlooked it, but I would be very interested to have a look at the lmod – hook you implemented for the lmod subcategories. Could you please share a link, if it’s ‘git-able’? One thing about the EB installation for plain HMNS. The module method to install EB instead of utilizing pip is perfectly fine? (as long as the environment is set-up correctly) Cheers, -Frank From: [email protected] <[email protected]> On Behalf Of Alan O'Cais Sent: Wednesday, 9 November 2022 17:27 To: [email protected] Subject: Re: [easybuild] CategorizedHMNS: easybuild installation method Hi Frank, CategorizedHMNS is not widely used (as far as I know) so you there may be some issues lurking there. Plain HMNS is much more widely used and I'd say a better choice. Additionally there's a new feature in Lmod that just got released that allows us to define multiple categories inside a module file (EasyBuild currently only allows one "moduleclass"). I haven't added support for it yet in EB but it's something I want to look at really soon. The plan would be that you use an EB hook to inject the categories that you want for a piece of software (based off some mapping that you store). This would add the categories to the module file and then you use Lmod to search for software based on categories. You use `module cat` to see available categories, `module cat <category name>` to show software in a category and then `module spider <software name>` to see how to load (versions of) that software (including any gateway modules). You can also use Lmod hooks with categories, for example I can imagine wanting to hide modules of a certain category for users in certain groups. Personally, I've implemented an Lmod hook that allows me to have subcategories so I can implement a complete taxonomy. Hope that helps, Alan On Wed, 9 Nov 2022 at 16:37, Heckes, Frank <[email protected] <mailto:[email protected]> > wrote: Hi all, The latest and also the previous tutorials recommends upon using HMNS: ‘. . . We strongly recommend using an EasyBuild installation that was <https://easybuilders.github.io/easybuild-tutorial/2022-isc22/installation/#method-1-using-pip-recommended> installed via "pip install" or "pip3 install" in this part of the tutorial. . . .’ (in <https://easybuilders.github.io/easybuild-tutorial/2022-isc22/module_naming_schemes/> https://easybuilders.github.io/easybuild-tutorial/2022-isc22/module_naming_schemes/) Does the recommendation also apply to ‘production’ environments or is this only a didactical safety set-up to avoid the clashes resulting from eventually existing installation with flat namespace or other modules? My question is, can I use the module installation procedure for CategorizedHMNS builds without running into problems, as long as I follow the donts described in the page above ? Many thanks in advance. Cheers, -Frank Heckes
smime.p7s
Description: S/MIME cryptographic signature
