-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Open crate files readonly first #3259
Conversation
This allows Cargo to work with read-only `CARGO_HOME` directories where the cache was prepared ahead of time. Closes rust-lang#3256
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ Thanks! |
📌 Commit 27e439c has been approved by |
⌛ Testing commit 27e439c with merge 4cf71cb... |
💥 Test timed out |
@bors: retry force clean On Tue, Nov 8, 2016 at 7:01 AM, bors notifications@github.com wrote:
|
Open crate files readonly first This allows Cargo to work with read-only `CARGO_HOME` directories where the cache was prepared ahead of time. Closes #3256
☀️ Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
This allows Cargo to work with read-only
CARGO_HOME
directories where thecache was prepared ahead of time.
Closes #3256