Add med libraries

[jschueller]

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.

[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/medcoupling, recipes/medfile) and found it was in an excellent condition.

[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/medcoupling, recipes/medfile, recipes/salome-med, recipes/salome-medcoupling) and found it was in an excellent condition.

[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/salome-med, recipes/salome-medcoupling) and found it was in an excellent condition.

[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/salome-med, recipes/salome-medcoupling) and found some lint.

Here's what I've got...

For recipes/salome-medcoupling:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [48]

[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/salome-med, recipes/salome-medcoupling) and found it was in an excellent condition.

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

[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/salome-med, recipes/salome-medcoupling) and found it was in an excellent condition.

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

For recipes/salome-medcoupling:

• The boost-cpp output has been superseded by libboost-devel (as of 1.82), which now comes with a run-export (on libboost) as well. In case you only needed the boost headers, you should use libboost-headers.

[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/salome-med, recipes/salome-medcoupling) and found it was in an excellent condition.

[jschueller]

ping @conda-forge/help-c-cpp

[xhochy]

Please include this as additional sources in the recipe.

[xhochy]

Please add a pip check call

[Krande]

Hey, @jschueller!

Have you seen the existing libmed feedstock https://github.com/conda-forge/libmed-feedstock which also represents the med library?

If there is something missing in the libmed feedstock (we have for example not released med v9.11 version yet, just the v9.10) we would be happy to collaborate on making improvements to libmed to fullfill your requirements.

FYI: We are also making an effort to add medcoupling (see #24378)

[jschueller]

see #24378

[jschueller]

hi, for libmed it seems my patch was way simpler than yours

[Krande]

@jschueller That's interesting! If you could create a PR for the libmed feedstock with your simplified patches we can take a look more closely on the differences there?