Adding recipe for knem-headers

[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 wanted to let you know that I linted all conda-recipes in your PR (recipes/knem-headers/meta.yaml) and found some lint.

Here's what I've got...

For recipes/knem-headers/meta.yaml:

• There are 3 too many lines. There should be one empty line at the end of the file.

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

[j34ni]

The knem project comprises multiple components, including a user-space library and a crucial kernel module that facilitates efficient memory copy operations at the kernel level. This package specifically provides the knem_io.h header from the knem project, allowing other software, like UCX, to interface with the knem kernel module, enabling high-performance communication in distributed computing environments.

[xhochy]

If these are only headers, there should be no runtime dependency.

[j34ni]

OK

[j34ni]

@xhochy Is that OK now?