conda-forge / conda-forge/conda-forge.github.io

Document the standard practice for `lib`, `lib-dev`, and `lib-static` packages

Open
#1,897 2 comments 0 reactions 0 assignees View on GitHub
Docs enhancement
Dominant language
JavaScript
Stars
170
Forks
320
Avg merge
2d 10h
Merged PRs (30d)
5

Description

### Where should the content be added?

_No response_

### What should be added?

Every time I encounter this discussion it gets me, and given the same discussions scattered everywhere (ex: [here](https://github.com/conda-forge/staged-recipes/pull/21901#issuecomment-1415931866) and [here](https://github.com/conda-forge/openblas-feedstock/issues/134#issuecomment-1083482954)) I assume it's worth documenting the Linux distro practice:
- `lib`: Only the runtime shared library `libxyz.so.X` & `libxyz.so.X.Y.Z`
- `lib-dev`: Symlinks to the shared library, `libxyz.so`, plus the library headers
- `lib-static`: Contains the static libraries `libxyz.a` or `libxyz_static.a`

There may be other subtle changes needed (ex: `run_exports`). Feel free to add more details and formalize this for conda-forge needs.

### Additional information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.