Skip to content
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

Yank all broken pkg-config versions from crates.io #62

Closed
klausi opened this issue Apr 1, 2018 · 2 comments
Closed

Yank all broken pkg-config versions from crates.io #62

klausi opened this issue Apr 1, 2018 · 2 comments

Comments

@klausi
Copy link

klausi commented Apr 1, 2018

On https://crates.io/crates/pkg-config/versions everything below v0.3.2 does not compile with recent Rust versions. They should all be yanked so that cargo only installs working minimal versions.

@alexcrichton
Copy link
Member

Thanks for the report! I commented over on the Cargo PR though in that I don't think this is quite the right solution, so I'm going to close this.

@kornelski
Copy link
Contributor

kornelski commented Dec 4, 2021

This is still an ecosystem-wide problem. It's relatively common for crates to specify pkg-config = "0.3", and this breaks min-versions.

Inability to rely on min-versions causes headaches with maintaining MSRV. For example users or zeroize resort to requiring >=1, <1.4 or =1.3. The newly added package.rust manifest property helps alert users about the problem, but util it starts influencing dependency resolution, it won't solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants