We use the hooks system to handle almost all of the site changes. There is some examples in the contrib dir.
We also have our own repo of things (both easyconfigs/blocks and of course the hooks). The easyconfigs/blocks there are usually only kept until they appear in the next release. ________________________________________ From: [email protected] on behalf of Schmitt,Felix Sent: Thursday, May 25, 2023 14:29 To: [email protected] Subject: [easybuild] Managing Site-specific Easyconfigs Dear colleagues, since we sometimes have to make site-specific changes to easyconfigs, I would like to draw on your collective wisdom regarding how to manage these best. Would you advise keeping them in a branch of our clone of the upstream repo or in an entirely separate repo, and why? We only have 3-5 IT staff working with Easybuild. Users typically do not install their own software. However, there might be some power users writing their own easyconfigs and willing to submit PRs. Thus, having the possibility to do the eb --new-pr workflow might come in handy. Thanks in advance for your suggestions! Cheers, Felix -- Dr. Felix Schmitt, M.A. Head of IT Institute for High Energy Physics (HEPHY) Austrian Academy of Sciences (ÖAW) https://hephy.at HPC User Support Engineer Cloud Infrastructure Platform (CLIP) Vienna BioCenter (VBC) https://vbc.ac.at e-mail: [email protected] [email protected] phone: +43 1 79730 3737
