Why gitignore Cargo.lock file?

riker-rs / riker

Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.

https://riker.rs

MIT License

1.02k stars 69 forks source link

Why gitignore Cargo.lock file? #88

Open Tirka opened 4 years ago

Tirka commented 4 years ago

I dont think it’s a good idea to drop info about exact versions of project’s dependencies out of repository

hardliner66 commented 4 years ago

It's good practice to not commit lock files when developing libraries See: https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries

leenozara commented 4 years ago

Recommended:

If you’re building a non-end product, such as a rust library that other rust packages will depend on, put Cargo.lock in your .gitignore. If you’re building an end product, which are executable like command-line tool or an application, or a system library with crate-type of staticlib or cdylib, check Cargo.lock into git.