Add GROMACS easyconfig template with software-commit#2
Conversation
|
Instance
|
software-commit
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
Co-authored-by: Bob Dröge <b.e.droge@rug.nl>
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
…MACS-2024.3-foss-2023b-software-commit.eb
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
How do we deal with this? It's a bit of a hassle to update it for every commit/build, so maybe we should just completely ignore/remove them? |
I think we'll have to ignore them... That's what I did for ESPResSo. I'm convinced now that I pushed the wrong GROMACS easyconfig, because I installed it locally from a commit...! Anyway, we can make this one work. |
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
Co-authored-by: Bob Dröge <b.e.droge@rug.nl>
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
|
Staging PR merged |
|
Module is in place: |
|
PR merged! Moved |
This follows the same approach as #1 and adds an easystack file for
GROMACSwithsoftware-committo a release that is known to work (it's the same that is already onsoftware.eessi.io).The easyconfig file also only needed minor changes. I included the patches, which works, and should mirror a scenario where a developer wants to also ship a patch to their dev version.