cargo-outdated: 0.9.1 -> 0.9.5
Upstream is now vendoring the Cargo.lock file for reproducible app builds, so we can now remove the patching workaround. However, they're missing a git tag, so we have to do some work to find the right git commit.
This commit is contained in:
parent
7695e9e1fa
commit
66e5cc0bd2
File diff suppressed because it is too large
Load Diff
@ -2,20 +2,19 @@
|
||||
|
||||
rustPlatform.buildRustPackage rec {
|
||||
pname = "cargo-outdated";
|
||||
version = "0.9.1";
|
||||
version = "0.9.5";
|
||||
|
||||
src = fetchFromGitHub {
|
||||
owner = "kbknapp";
|
||||
repo = pname;
|
||||
rev = "v${version}";
|
||||
sha256 = "02gsarwm4gjkr9m4sfbjwp37xmqhch8qpyy027bxqkg8iyipxm69";
|
||||
# This is the git commit that produced 0.9.5, according to crates.io, but
|
||||
# the tag is missing in git. See here for details:
|
||||
# https://github.com/kbknapp/cargo-outdated/issues/206
|
||||
rev = "7685da3265749bb7ae2b436a132f51d19b409bff";
|
||||
sha256 = "08prksns7d3g7ha601z8p28p36rg44rjl5ph76vg6nriww96zzca";
|
||||
};
|
||||
|
||||
cargoPatches = [ ./cargo-lock.patch ];
|
||||
# Delete this on next update; see #79975 for details
|
||||
legacyCargoFetcher = true;
|
||||
|
||||
cargoSha256 = "1ywmrvkwwwwh99l4j8vc4cyk8qjd0jx8hn68yr2h31ya1bzcqbd1";
|
||||
cargoSha256 = "0kxfavyd9slpp2kzxhjp47q1pzw9rlmn7yhxnjsg88sxbjxfzv95";
|
||||
|
||||
nativeBuildInputs = [ pkgconfig ];
|
||||
buildInputs = [ openssl ]
|
||||
|
@ -1,18 +0,0 @@
|
||||
#!/bin/sh
|
||||
|
||||
# This updates cargo-lock.patch for the cargo-outdated version listed in default.nix.
|
||||
|
||||
set -eu -o verbose
|
||||
|
||||
here=$PWD
|
||||
version=$(cat default.nix | grep '^ version = "' | cut -d '"' -f 2)
|
||||
checkout=$(mktemp -d)
|
||||
git clone -b "v$version" --depth=1 https://github.com/kbknapp/cargo-outdated "$checkout"
|
||||
cd "$checkout"
|
||||
|
||||
cargo generate-lockfile
|
||||
git add -f Cargo.lock
|
||||
git diff HEAD -- Cargo.lock > "$here"/cargo-lock.patch
|
||||
|
||||
cd "$here"
|
||||
rm -rf "$checkout"
|
Loading…
Reference in New Issue
Block a user