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
Please consider publishing Cargo.lock, otherwise it's impossible to do a cargo build --locked (handy for reproducible builds) on a tarball acquired from crates.io. This is how.
Alternatively, if you're short on time or don't want to deal with nightly features, a git tag aligned with the version published on crates.io could suffice.
As I understand it, this feature is now on by default: rust-lang/cargo#7026. My guess is that it's just a matter of me not having issued a release since that were the case. I will issue a new release, and also tag all past releases!
Please consider publishing
Cargo.lock
, otherwise it's impossible to do acargo build --locked
(handy for reproducible builds) on a tarball acquired from crates.io. This is how.Alternatively, if you're short on time or don't want to deal with nightly features, a git tag aligned with the version published on crates.io could suffice.
P.S. Published on AUR:
proximity-sort
The text was updated successfully, but these errors were encountered: