greg/nix-bitcoin
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
94672e8f34
nix-bitcoin/pkgs/electrs/default.nix

30 lines
1.0 KiB
Nix
Raw Normal View History

Get electrs source tarball with gpg verified sha256 and corresponding helper script move script to pkg dir, add hint to script in pkg def remove unneeded script deps add extended bash error checking rename DIR -> TMPDIR remove TMPDIR on exit strip whitespace, simplify comments gpg2 -> gpg latesttagelectrs -> latest tmpdir: don't use XDG_RUNTIME_DIR XDG_RUNTIME_DIR is often in RAM and shouldn't be used for larger workloads like repo downlaods verify fingerprint of the imported key remove trailing '-' in output simplify output Hide --fetch-key output Output is not relevant to user, looks better without it More accurately describe ./get-sha256 function User might think that ./get-sha256 automatically updates sha256 in default.nix Fetch key from sks keyservers instead of keybase.io Using --recv-key simplifies getting the right key, and only the right key, greatly. I try to refrain from using sks keyservers, but the certificate spamming attack shouldn't be an issue in this case because we create a temporary keychain just for the verificaiton. remove unneeded cargoDepsHook Make clang nativeBuildInput instead of buildInput
2020-04-14 02:04:03 -07:00
{ lib, rustPlatform, llvmPackages, fetchurl, pkgs }:
electrs: 0.7.1 -> 0.8.3 Use buildRustPackage instead of buildRustCrate (via crate2nix). buildRustPackage builds the whole executable and its libraries in a single `cargo build` process. With the create2nix approach each library is built in a separate derivation, directly using rustc instead of the cargo wrapper. Benefits of buildRustPackage: - Much simpler to maintain - Package derivation evaluates much faster Benefits of crate2nix: - Build can be distributed over multiple build hosts - Better sharing of common dependencies between different builds - More fine-grained rebuilding on build failures In nixpkgs buildRustPackage is used for almost all Rust pkgs, it's also a better fit for our use case.
2020-03-04 09:08:55 -08:00
rustPlatform.buildRustPackage rec {
pname = "electrs";
version = "0.8.3";
Get electrs source tarball with gpg verified sha256 and corresponding helper script move script to pkg dir, add hint to script in pkg def remove unneeded script deps add extended bash error checking rename DIR -> TMPDIR remove TMPDIR on exit strip whitespace, simplify comments gpg2 -> gpg latesttagelectrs -> latest tmpdir: don't use XDG_RUNTIME_DIR XDG_RUNTIME_DIR is often in RAM and shouldn't be used for larger workloads like repo downlaods verify fingerprint of the imported key remove trailing '-' in output simplify output Hide --fetch-key output Output is not relevant to user, looks better without it More accurately describe ./get-sha256 function User might think that ./get-sha256 automatically updates sha256 in default.nix Fetch key from sks keyservers instead of keybase.io Using --recv-key simplifies getting the right key, and only the right key, greatly. I try to refrain from using sks keyservers, but the certificate spamming attack shouldn't be an issue in this case because we create a temporary keychain just for the verificaiton. remove unneeded cargoDepsHook Make clang nativeBuildInput instead of buildInput
2020-04-14 02:04:03 -07:00
src = fetchurl {
url = "https://github.com/romanz/electrs/archive/v${version}.tar.gz";
# Use ./get-sha256.sh to fetch latest (verified) sha256
sha256 = "6a00226907a0c36b10884e7dd9f87eb58123f089977a752b917d166af072ea3d";
Update electrs to version 0.6.2 with pinned dependencies
2019-05-23 07:03:56 -07:00
};
electrs: 0.7.1 -> 0.8.3 Use buildRustPackage instead of buildRustCrate (via crate2nix). buildRustPackage builds the whole executable and its libraries in a single `cargo build` process. With the create2nix approach each library is built in a separate derivation, directly using rustc instead of the cargo wrapper. Benefits of buildRustPackage: - Much simpler to maintain - Package derivation evaluates much faster Benefits of crate2nix: - Build can be distributed over multiple build hosts - Better sharing of common dependencies between different builds - More fine-grained rebuilding on build failures In nixpkgs buildRustPackage is used for almost all Rust pkgs, it's also a better fit for our use case.
2020-03-04 09:08:55 -08:00
# Needed for librocksdb-sys
Get electrs source tarball with gpg verified sha256 and corresponding helper script move script to pkg dir, add hint to script in pkg def remove unneeded script deps add extended bash error checking rename DIR -> TMPDIR remove TMPDIR on exit strip whitespace, simplify comments gpg2 -> gpg latesttagelectrs -> latest tmpdir: don't use XDG_RUNTIME_DIR XDG_RUNTIME_DIR is often in RAM and shouldn't be used for larger workloads like repo downlaods verify fingerprint of the imported key remove trailing '-' in output simplify output Hide --fetch-key output Output is not relevant to user, looks better without it More accurately describe ./get-sha256 function User might think that ./get-sha256 automatically updates sha256 in default.nix Fetch key from sks keyservers instead of keybase.io Using --recv-key simplifies getting the right key, and only the right key, greatly. I try to refrain from using sks keyservers, but the certificate spamming attack shouldn't be an issue in this case because we create a temporary keychain just for the verificaiton. remove unneeded cargoDepsHook Make clang nativeBuildInput instead of buildInput
2020-04-14 02:04:03 -07:00
nativeBuildInputs = [ llvmPackages.clang ];
electrs: 0.7.1 -> 0.8.3 Use buildRustPackage instead of buildRustCrate (via crate2nix). buildRustPackage builds the whole executable and its libraries in a single `cargo build` process. With the create2nix approach each library is built in a separate derivation, directly using rustc instead of the cargo wrapper. Benefits of buildRustPackage: - Much simpler to maintain - Package derivation evaluates much faster Benefits of crate2nix: - Build can be distributed over multiple build hosts - Better sharing of common dependencies between different builds - More fine-grained rebuilding on build failures In nixpkgs buildRustPackage is used for almost all Rust pkgs, it's also a better fit for our use case.
2020-03-04 09:08:55 -08:00
LIBCLANG_PATH = "${llvmPackages.libclang}/lib";
Update electrs to version 0.6.2 with pinned dependencies
2019-05-23 07:03:56 -07:00
electrs: fix conditional cargoSha256
2020-05-02 09:07:21 -07:00
cargoSha256 = if builtins.pathExists "${pkgs.path}/pkgs/build-support/rust/fetchcargo.nix" then
# nixpkgs ≤ 20.03
electrs: enable unstable build, pin pkg to unstable stable's buildRustPackage is painfully slow when evaluating (adds >1 sec even on a fast machine). This is fixed (https://github.com/NixOS/nixpkgs/pull/69274) in unstable.
2020-03-04 09:08:56 -08:00
"19qs8if8fmygv6j74s6iwzm534fybwasjvmzdqcl996xhg75w6gi"
else
# for recent nixpkgs with cargo-native vendoring (introduced in nixpkgs PR #69274)
"1x88zj7p4i7pfb25ch1a54sawgimq16bfcsz1nmzycc8nbwbf493";
Update electrs to version 0.6.2 with pinned dependencies
2019-05-23 07:03:56 -07:00
electrs: 0.7.1 -> 0.8.3 Use buildRustPackage instead of buildRustCrate (via crate2nix). buildRustPackage builds the whole executable and its libraries in a single `cargo build` process. With the create2nix approach each library is built in a separate derivation, directly using rustc instead of the cargo wrapper. Benefits of buildRustPackage: - Much simpler to maintain - Package derivation evaluates much faster Benefits of crate2nix: - Build can be distributed over multiple build hosts - Better sharing of common dependencies between different builds - More fine-grained rebuilding on build failures In nixpkgs buildRustPackage is used for almost all Rust pkgs, it's also a better fit for our use case.
2020-03-04 09:08:55 -08:00
meta = with lib; {
description = "An efficient Electrum Server in Rust";
homepage = "https://github.com/romanz/electrs";
license = licenses.mit;
maintainers = with maintainers; [ earvstedt ];
Update electrs to version 0.6.2 with pinned dependencies
2019-05-23 07:03:56 -07:00
};
}
Reference in New Issue Copy Permalink