Add recipe for metatensor

[Luthaf]

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.

---

This is adding a recipe for the core library in https://github.com/lab-cosmo/metatensor. A future PR will add another recipe for the torch bindings which live in the same repo (as well as the Python bindings to both the -core and -torch versions of the code).

This package is implemented in Rust, but builds with CMake and generally behaves like a C++ package from an outside point of view.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [6, 7, 9, 10, 12, 13, 14]
• The following maintainers have not yet confirmed that they are willing to be listed here: PicoCentauri, luthaf. Please ask them to comment on this PR if they are.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• The following maintainers have not yet confirmed that they are willing to be listed here: PicoCentauri. Please ask them to comment on this PR if they are.

[Luthaf]

The windows error is related to our CMake script, I'll check it. The osx error is a bit stranger, and seems related to MACOSX_DEPLOYMENT_TARGET=10.9? But it should automatically be set to 10.12 according to https://conda-forge.org/news/2024/01/29/rust-175-osx-sdk/. Is there anything else I should be doing here?

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• 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 . from the recipe directory.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• The following maintainers have not yet confirmed that they are willing to be listed here: PicoCentauri. Please ask them to comment on this PR if they are.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• The following maintainers have not yet confirmed that they are willing to be listed here: PicoCentauri. Please ask them to comment on this PR if they are.
• The source section contained an unexpected subsection name. patch is not a valid subsection name.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• The following maintainers have not yet confirmed that they are willing to be listed here: PicoCentauri. Please ask them to comment on this PR if they are.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• 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 . from the recipe directory.

[conda-forge-webservices]

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/metatensor) and found some lint.

Here's what I've got...

For recipes/metatensor:

• The following maintainers have not yet confirmed that they are willing to be listed here: PicoCentauri. Please ask them to comment on this PR if they are.

[Luthaf]

@conda-forge/help-rust and @conda-forge/help-c-cpp, ready for review!

[xhochy]

Please also bundle third-party rust licenses using cargo-bundle-licenses (see other Rust PRs for that).

[PicoCentauri]

I am willing to be listed as a maintainer of the metatensor conda package.

[conda-forge-webservices]

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/metatensor) and found it was in an excellent condition.

[Luthaf]

@conda-forge/help-rust and @conda-forge/help-c-cpp, this is ready for a second round of review =)