-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
cargo build
and cargo install -f
write Cargo.lock
differently
#3133
Comments
Interesting! Could you gist the diff between the two lock files? |
alexcrichton
added a commit
to alexcrichton/cargo
that referenced
this issue
Sep 30, 2016
Prevent lock files from oscillating. Closes rust-lang#3133
Thanks! Confirms my suspicions and fixed in #3146 |
bors
added a commit
that referenced
this issue
Oct 6, 2016
Use workspaces during `cargo install` Prevent lock files from oscillating. Closes #3133
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given the following repo: https://github.com/oconnor0/build-your-own-editor/tree/24586c991a7faa513723595164df544e7c81ae73
When I run
cargo build
from the root, theCargo.lock
is written out one way.When I run
cargo install -f
from the root, theCargo.lock
is written in a different way.They are consistent - so that if I run
cargo build
, git will show no changed. If I then runcargo install -f
, I see changes inCargo.lock
. Runningcargo build
again shows no changes.There are only two
Cargo.toml
in the repository:At the root:
Inside the
textbox
directory:The text was updated successfully, but these errors were encountered: