Adding shell package

[prsabahrami]

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 I found some lint.

File-specific lints and/or hints:

• recipes/shell/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: wolfv. 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 wanted to let you know that I linted all conda-recipes in your PR (recipes/shell/meta.yaml) and found some lint.

Here's what I've got...

For recipes/shell/meta.yaml:

• ❌ The recipe must have some tests.

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

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

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

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

For recipes/shell/meta.yaml:

• ℹ️ libgcc-ng has been superseded by libgcc. Note however, that except in truly exceptional cases, you should not have to add this manually; you can rely on the fact that {{ compiler("c") }} and {{ compiler("cxx") }} will always create the correct run-export for this. If you need to ignore the run-export for whatever reason, the best way to do it is:

  build:
    ignore_run_exports_from:
      - {{ compiler("c") }}    # depending on which...
      - {{ compiler("cxx") }}  # ... compilers you use

• ℹ️ libgfortran-ng has been superseded by libgfortran. Note however, that except in truly exceptional cases, you should not have to add this manually; you can rely on the fact that {{ compiler("fortran") }} will always create the correct run-export for this. If you need to ignore the run-export for whatever reason, the best way to do it is:

  build:
    ignore_run_exports_from:
      - {{ compiler("fortran") }}

• ℹ️ libstdcxx-ng has been superseded by libstdcxx. Note however, that except in truly exceptional cases, you should not have to add this manually; you can rely on the fact that {{ compiler("cxx") }} will always create the correct run-export for this. If you need to ignore the run-export for whatever reason, the best way to do it is:

  build:
    ignore_run_exports_from:
      - {{ compiler("cxx") }}

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

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

Here's what I've got...

For recipes/shell/meta.yaml:

• ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [28, 30, 31, 32]

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

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

Here's what I've got...

For recipes/shell/meta.yaml:

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

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

[prsabahrami]

@conda-forge/help-rust I seem to be getting some errors on linux and osx. When I try simple cargo install --path . the executable is not being found afterwards. However, when I build and move the executable to $PREFIX/bin I get different errors.

[wolfv]

You can use this syntax for win and unix (because Jinja works the same!).

It would be good to add --no-track to not create overlapping $PREFIX/crates2.json files.