You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, this makes downstream packaging easier in some places, like nixpkgs, where a Cargo.lock is mandatory for Rust packages. I would love to package the xtr utility for nixpkgs, but the lack of Cargo.lock in your repository complicates things somewhat (while an out-of-tree Cargo.lock can be provided, it would be nice to have it provided in the repository).
Since this package provides an executable binary, it makes sense to provide a Cargo.lock in this repository even under the old guidelines.
The text was updated successfully, but these errors were encountered:
Current Rust best practices recommend committing
Cargo.lock
even for libraries: https://blog.rust-lang.org/2023/08/29/committing-lockfiles.htmlAdditionally, this makes downstream packaging easier in some places, like nixpkgs, where a Cargo.lock is mandatory for Rust packages. I would love to package the
xtr
utility for nixpkgs, but the lack ofCargo.lock
in your repository complicates things somewhat (while an out-of-treeCargo.lock
can be provided, it would be nice to have it provided in the repository).Since this package provides an executable binary, it makes sense to provide a
Cargo.lock
in this repository even under the old guidelines.The text was updated successfully, but these errors were encountered: