-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking pkg-config provides #295047
Comments
CC @hamishmack and @sternenseemann, as I imagine both Haskell infrastructures have a pretty good list initial list we could use to get started on this. |
We have a lookup table, but it is very aggressive: It maps names to nixpkgs attribute paths, but those names may either be the name you'd pass to |
nix-index can be used to find all the pc files
The output format is
|
@Ericson2314 pinged me because of our work on Riff.sh. We looked at doing something similar back in September, but never took steps on it. Maybe this is useful info:
We were planning on doing it through something like nix-index instead of adding metadata preemptively to Nixpkgs. But I think either way could work. |
And I was totally unaware that Go leverages this too! Good to see more newer languages going with pkg-config out of the box. |
That is merged so this is done! Just need to go annotate all the packages now :) |
Issue description
The world really needs to know which distro package provides which pkg-config package. This is important because pkg-config package names are the defacto way to refer to C / "foreign" libraries in a distro-agnostic way, and we generally want upstream package managers to use them vs more ad-hoc methods.
This would be really good for upstream language-based tools, our lang2nix tools, really everybody.
In repology/repology-updater#1309, the Repology maintainer @AMDmi3 has kindly offered:
That sounds amazing!
Goal
We should have
meta.pkg-config
field, which is either a single string or list of strings.pc
file.CC @dcbaker
The text was updated successfully, but these errors were encountered: