Add hdf5-mpi - Ready for review

[j34ni]

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.

[github-actions]

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

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

[j34ni]

The hdf5-mpi package was created to provide HDF5 support with additional MPI implementations, specifically MVAPICH with UCX and OFI, which are not supported by the existing similar packages. This package targets HPC environments requiring these specific MPI builds, ensuring broader compatibility, flexibility, and performance tuning for users with advanced computing needs.

[conda-forge-admin]

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

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12629456484. 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/hdf5-mpi/meta.yaml) and found it was in an excellent condition.

[j34ni]

@conda-forge/staged-recipes

I've encountered some issues while working on this hdf5-mpi recipe in the staged-recipes repo. Here's a brief summary:

• I tried to remove the knem-headers directory since it was left there by mistake from previous work and is not related to my current hdf5-mpi recipe.
• This action caused the CI/CD linter to fail because it was looking for meta.yaml in the now-missing knem-headers directory.
• To resolve the immediate CI/CD issue, I've restored the original files in knem-headers, and now the linter is happy.

However, knem-headers remains unrelated to my work on hdf5-mpi. Could someone please advise on the best way to clean up this situation without disrupting the CI/CD process?

Thank you for your assistance.

[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!