4816a73bb5
--frozen is stricter than we need in Nixpkgs. If a Cargo.lock is slightly wrong, or (in my use case) if building a subproject that is not a member of the top-level workspace, but the correct Cargo.lock can be entirely resolved from the existing top-level Cargo.lock, it should be deterministic, and shouldn't cause any problems, to let cargo generate the new Cargo.lock. This should result in less need to bother upstreams about fixing their Cargo.lock files in cases where they could have been automatically fixed. |
||
|---|---|---|
| .. | ||
| cargo-build-hook.sh | ||
| cargo-check-hook.sh | ||
| cargo-install-hook.sh | ||
| cargo-nextest-hook.sh | ||
| cargo-setup-hook.sh | ||
| default.nix | ||
| maturin-build-hook.sh | ||
| rust-bindgen-hook.sh | ||