2 ms·

But does not cargo bottom out at libraries like https://crates.io/crates/openssl-sys/0.9.75 https://crates.io/crates/openssl-sys/0.9.75, where you do need addit

But does not cargo bottom out at libraries like https://crates.io/crates/openssl-sys/0.9.75 https://crates.io/crates/openssl-sys/0.9.75, where you do need addition (non-managed) dependencies? I would be surprised that the more "conservative" linux distros didn't have a complete, deduplicated and unvendored tree (only encountering issues around binary firmware and similar), whereas from my minimal rust knowledge, cargo's reqwest metadata is incomplete. It's the incompleteness I'm suggesting is a problem (I'm more familiar with Python and wheels, where there are substantial non-Python dependencies people forget about), not the number of dependencies (though that's not great either).

pornel 4y ago
The "system dependency" wrapper crates are unfortunately dependent on the environment outside of Cargo's view. The Rewrite-In-Rust Strike Force is working on eliminating this problem ;) Cargo/crates.io has a publicly available index of every crate with every dependency. `cargo tree` lists everything in your project. `Cargo.lock` contains inventory of every package used in the build, including their checksums. See https://lib.rs/stats https://lib.rs/stats