Add QCDLoop Fortran

[matthewfeickert]

• Add QCDLoop v1.98 in Fortran.
  • c.f. https://qcdloop.fnal.gov/
• Permission to license QCDLoop as MIT (previously unlicensed) was given by author R. Keith Ellis via email on 2025-02-03.
• This Fortran version of QCDLoop is no longer maintained but is still required for legacy particle physics software. The reimplimentation in C++ is https://github.com/conda-forge/qcdloop-feedstock.
  • c.f. Package mg5amcnlo dependencies hep-packaging-coordination/packaging-hep-simulation-stack#3

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• [N/A] If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
  • Package only provides a static library but CFEP is followed.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[matthewfeickert]

@chrisburr We already have the C++ version as qcdloop (https://github.com/conda-forge/qcdloop-feedstock). Would you suggest qcdloop-fortran or just ql (the library name)?

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/qcdloop-fortran/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/qcdloop-fortran/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13122465480. Examine the logs at this URL for more detail.}

[chrisburr]

Would you suggest qcdloop-fortran or just ql (the library name)?

I would say qcdloop-fortran. I think it's a bit too niche to justify a two character package name.

[matthewfeickert]

@conda-forge/staged-recipes, ready for review! This is a fortran recipe.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!