Adding isis_core

[amystamile-usgs]

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-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/isiscore/meta.yaml) and found some lint.

Here's what I've got...

For recipes/isiscore/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler.

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

[github-actions]

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

File-specific lints and/or hints:

• recipes/isiscore/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: acpaquette. 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/isiscore/meta.yaml) and found it was in an excellent condition.

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

[github-actions]

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

[amystamile-usgs]

@conda-forge-admin, please restart ci

[amystamile-usgs]

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

[amystamile-usgs]

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

[traversaro]

Why such strict pins?

[acpaquette]

Hi @traversaro, thanks for the quick review on this. This recipe is reflective of conda-forge before the automatic migration mechanisms were in place, so the restrictive pinning was a solution to prevent dependencies from changing too much rather than release the software every time a dependency updated. We will update the recipe to be more in line with current conda-forge feedstocks

[traversaro]

Are you sure you actually need mesalib in host?

[traversaro]

Why such strict pins? This will interefere with the conda-forge ABI migration branch mechamism.

[traversaro]

Why such strict pin?

[traversaro]

As the package itself is called qt6-main, probably we can drop the version specifier?

[traversaro]

Isn't this already handled by the run_exports?

[traversaro]

Can we wait for the actual release? conda-forge has specific policies for pre-releases, see https://conda-forge.org/docs/maintainer/knowledge_base/#pre-release-builds .

[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/isiscore/meta.yaml) and found some lint.

Here's what I've got...

For recipes/isiscore/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler.

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