-
Notifications
You must be signed in to change notification settings - Fork 36
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
Why duplicate Cargo caches? #25
Comments
@SimonSapin The intent is to protect against Cargo metadata format changes when switching between toolchains that run different versions of Cargo. |
Is there a reason for Cargo to be part of the toolchains? Shouldn’t the latest Cargo be able to use any 1.0+ rustc? |
@SimonSapin It's part of the toolchain because we want people to install Cargo when they install Rust. I hadn't considered whether the latest Cargo should be able to use any 1.0+ rustc but I think it should be so. |
Related automation issue about Cargo + old rustc compat rust-lang/cargo#1276 |
This actually causes a major problem for me: when I upgrade toolchains I am forced to redownload the registry and crates for projects that previously built. This often results in me being forced onto the network while I'm away from the office. I think this should probably be changed. |
From README.md:
How is this beneficial? It means that Cargo’s download cache is duplicated, wasting bandwidth and disk space.
The text was updated successfully, but these errors were encountered: