Remove Cargo.lock from version control

The Cargo.lock file has been source of much annoyance and does not
really serve it's purpose in crosvm anyway. Both Android and ChromeOS
builds will not use Cargo.lock files but use their own infra to pin
dependencies to fixed versions.
Cargo.lock files are only used for development builds, but can cause
frequent merge issues, especially once our hacky 'setup_cros_cargo.sh'
script is involed.

Since we are planning to migrate towards bazel in the not-so-far future,
the easiest short term plan is to just remove Cargo.lock from version
control and deal with potential discrepancies in development builds.

BUG=None
TEST=None

Change-Id: I23736a61a4cc8131888d5ee2c19793066267f608
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3140584
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
This commit is contained in:
Dennis Kempin 2021-09-03 15:05:41 -07:00 committed by Commit Bot
parent ab4be4298a
commit 3b7a45792d
2 changed files with 0 additions and 1442 deletions

1
.gitignore vendored
View file

@ -4,7 +4,6 @@ target/
**/*.sw[po]
**/*.orig
**/Cargo.lock
!/Cargo.lock
lcov.info
.idea
.vscode

1441
Cargo.lock generated

File diff suppressed because it is too large Load diff