4 ms·
They're pulled from crates.io. I suppose it works as every other dependency manager, except that you can't have a left-pad because crates can't be removed. In
by GrayShade 7y ago
They're pulled from crates.io. I suppose it works as every other dependency manager, except that you can't have a left-pad because crates can't be removed.
In this specific case, most dependencies are authored by people well-known and trusted in the community. The Rust standard library is pretty well-rounded (not compared to Python sense, but it's not like JavaScript either), so they're not something like left-pad or is-odd.
You have there an error handling crate by the second most prolific Rust compiler contributor (if the counts are correct), an OAuth client, an HTTP one, a interactive line editor (like readline), _the_ serialization library in the ecosystem with its JSON support crate, a TOML config parser, the URL parser used by Servo and a crate for determining user paths on Unix.
- eb0la 7y agoWith cargo (Rust build tool) you don't need to use crates.io _always_ . For instance, you can target a repository and even a specific commit like this in gour cargo.toml file: [dependencies] package = { git = "https://github.com/...../something.git", rev = "commit_hash_like_9876541_for_instance" }
- GrayShade 7y agoYou can even host your own package registry, but I didn't think it would be worth mentioning in the context of that question.
- echelon 7y agoYou can still have your dependencies reference the source cargo packages, but overwrite it in a patch or vendor section. Don't specify the git repo directly in dependencies unless it's an unpublished crate.