Add GAMBIT

[matthewfeickert]

• Source code: https://github.com/GambitBSM/gambit_2.6
• License: BSD, but for some reason is missing an actual LICENSE file. :?
• Requirements: c.f. https://github.com/GambitBSM/gambit_2.6/tree/d102ac22cc2f75a3dbf93860907f321ce085262f?tab=readme-ov-file#compulsory
• Requester: @matthewfeickert
• Relevant build experts: @anderkve, @patscott

[patscott]

Thanks for interest @matthewfeickert. The license is at the end of README.md. You're right that it would be more traditional to give it its own file - we can do that in the next release.

[matthewfeickert]

The license is at the end of README.md

Yup, that's how I quickly checked it was BSD

You're right that it would be more traditional to give it its own file - we can do that in the next release.

That would be great to adopt in general. conda-forge requires that there's an actual license file (that is just the license, not the full README) as part of its packaging requirements, but I can add the license in the README as a patch file for the initial build.

The motivation for this project is to try to get as much of our high quality particle physics software on conda-forge as well so that we can have trivially installable multi-platform, yet platform specific optimized, installs of our tools (c.f. https://indico.cern.ch/event/1466101/contributions/6287842/).

@patscott once I PR this to https://github.com/conda-forge/staged-recipes/ and create a feedstock for it, would you, and any other members of the GAMBIT dev team, like to be added as maintainers of the conda-forge feedstock (which in terms of responsibility could mostly just be checking if the automated builds for each new release get kicked off okay and asking questions if things seem strange)?

[matthewfeickert]

Actually, if you can answer GambitBSM/gambit_2.6#4 first that would be useful.

[anderkve]

Also adding @ChrisJChang to the conversation, as he is the current convenor of the GAMBIT Core development group.

I'm not too familiar with conda-forge from before, but I'd be happy to help maintain the conda-forge feedstock.

[patscott]

Also adding @ChrisJChang to the conversation, as he is the current convenor of the GAMBIT Core development group.

I'm not too familiar with conda-forge from before, but I'd be happy to help maintain the conda-forge feedstock.

Same here -- I'm not very active as a GAMBIT dev any longer, but can still help out here and there. @ChrisJChang is definitely the most key person to include as a maintainer.

[ChrisJChang]

I can confirm that I am happy to be added as a maintainer.