Curiously, more and more Rust crates, mainly wrapper ones that depend on C/C++ libs, pull those in via the `vcpgkg` crate[1] in their `build.rs`. And I also saw

Curiously, more and more Rust crates, mainly wrapper ones that depend on C/C++ libs, pull those in via the `vcpgkg` crate[1] in their `build.rs`. And I also saw some that then use `pkgconfig`[2] as a fallback. I already fixed several `vcpgkg` ports as I started using this myself in several of my crates. 1. A package manager is only ever as good as its coverage of people's needs - packages wise. Forget usability, CLI, etc. If it covers the packages I need (and can actually build them) I'm happy to bite those bullets. 2. Having a single package manager for a language X certainly helps with 1. While any extra one that someone comes up with because they do not like the CLI/UX/"principles" of the existing one or whatever is a detriment to 1. [1] https://docs.rs/vcpkg/0.2.10/vcpkg/ https://docs.rs/vcpkg/0.2.10/vcpkg/ [2] https://docs.rs/pkg-config/0.3.19/pkg_config/ https://docs.rs/pkg-config/0.3.19/pkg_config/