Feat/add tardigrade_cmml

[NateAM]

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).
• 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.
• 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.

[NateAM]

@kbrindley will you comment if you are willing to be a maintainer?

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

• recipes/tardigrade_cmml/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: kbrindley. Please ask them to comment on this PR if they are.

[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/tardigrade_cmml/meta.yaml) and found it was in an excellent condition.

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

For recipes/tardigrade_cmml/meta.yaml:

• ℹ️ The boost output has been superseded by libboost-python-devel (as of 1.82), which now comes with a run-export (on libboost-python) as well.

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

[NateAM]

Blocked by #30240 , #30241 , #30242 , #30243 , #30244 , #30245 , and #30246

[kbrindley]

I am willing to be a maintainer

[stale]

Hi friend!

We really, really, really appreciate that you have taken the time to make a PR on conda-forge/staged-recipes! conda-forge only exists because people like you donate their time to build and maintain conda recipes for use by the community.

In an effort to maintain this repository and increase the signal-to-noise for open PRs, the maintainers of staged-recipes close excessively old PRs after six months. This PR will remain open for another month, and then will be closed.

If you'd like to keep it open, please comment/push and we will be happy to oblige! Note that very old PRs will likely need to be rebased on main so that they can be rebuilt with the most recent CI scripts. If you have any trouble, or we missed reviewing this PR in the first place (sorry!), feel free to ping the team using a special command in a comment on the PR to get the attention of the staged-recipes team.

Cheers and thank you for contributing to this community effort!

[github-actions]

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

[NateAM]

I want to keep this open. We're waiting for the conda-forge c++ team to review some other pull requests.

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/tardigrade_cmml/meta.yaml) and found some lint.

Here's what I've got...

For recipes/tardigrade_cmml/meta.yaml:

• ❌ The recipe is not parsable by any of the known recipe parsers (['conda-forge-tick (the bot)', 'conda-recipe-manager', 'conda-souschef (grayskull)']). Please check the logs for more information and ensure your recipe can be parsed.

For recipes/tardigrade_cmml/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-forge-tick (the bot). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ 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/22001171406. Examine the logs at this URL for more detail.}

[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/tardigrade_cmml/meta.yaml) and found it was in an excellent condition.

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

• conda-forge.yml:
  • lints:
    • Do not edit files outside of the recipes/ directory.

[NateAM]

@conda-forge-admin, please rerender

[github-actions]

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

[NateAM]

@conda-forge/help-c-cpp This is ready for review

[kbrindley]

because hydra has a run export and is present in the host section, you can probably rely on hydra to add it's runtime dependence implicitly. An explicit requirement here may actually duplicate the hydra spec in the runtime requirements