-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add Cargo.lock file #61
Comments
Besides that, things like |
Thank you so much for supporting |
@jhspetersson Great! While we're at it, can we get a new (maybe minor) release so me and other maintainers can package it? Thanks! |
@filalex77 done. New 0.6.7 release has arrived. Thanks for all the efforts on bringing |
Thanks! |
In the process of making changes to formulae in the Homebrew package manager, I noticed that fselect was one of a handful of Rust binary projects without a
Cargo.lock
file in version control. The Cargo book recommends the following (source):More information about the reasoning can be found in the "Why do binaries have Cargo.lock in version control, but not libraries?" section of the Cargo FAQ.
The
Cargo.lock
file helps package managers to keep builds reproducible, sincecargo install
simply uses the latest dependency versions unless the--locked
flag is added to the command, in which case it will use the versions outlined inCargo.lock
. Without aCargo.lock
file, there's a chance that a dependency update will break the build sometime in the future, which is something I've already encountered with other Rust binary projects.Would you please consider checking
Cargo.lock
into version control?The text was updated successfully, but these errors were encountered: