public
/
nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nixpkgs/pkgs/tools/package-management/nix-du/default.nix

32 lines
846 B
Nix
Raw Normal View History

nix-du: 0.2.0 -> 0.3.0
2018-11-03 03:08:23 -07:00
{ stdenv, fetchFromGitHub, rustPlatform, nix, boost, graphviz, darwin }:
rust: update docs on legacyCargoFetcher; remove unnecessary defaults As mentioned in #79975, the default on `legacyCargoFetcher` if left unspecified is now `false`.
2020-02-14 22:06:59 -08:00
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
rustPlatform.buildRustPackage rec {
treewide: name -> pname (#67513)
2019-08-31 04:41:23 -07:00
pname = "nix-du";
nix-du: 0.3.0 -> 0.3.1
2019-10-12 05:00:00 -07:00
version = "0.3.1";
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
src = fetchFromGitHub {
owner = "symphorien";
repo = "nix-du";
nix-du: 0.3.0 -> 0.3.1
2019-10-12 05:00:00 -07:00
rev = "v${version}";
sha256 = "149d60mid29s5alv5m3d7jrhyzc6cj7b6hpiq399gsdwzgxr00wq";
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
};
rust: update docs on legacyCargoFetcher; remove unnecessary defaults As mentioned in #79975, the default on `legacyCargoFetcher` if left unspecified is now `false`.
2020-02-14 22:06:59 -08:00
fetchcargo: use flat tar.gz file for vendored src instead of recursive hash dir This has several advantages: 1. It takes up less space on disk in-between builds in the nix store. 2. It uses less space in the binary cache for vendor derivation packages. 3. It uses less network traffic downloading from the binary cache. 4. It plays nicely with hashed mirrors like tarballs.nixos.org, which only substitute --flat hashes on single files (not recursive directory hashes). 5. It's consistent with how simple `fetchurl` src derivations work. 6. It provides a stronger abstraction between input src-package and output package, e.g., it's harder to accidentally depend on the src derivation at runtime by referencing something like `${src}/etc/index.html`. Likewise, in the store it's harder to get confused with something that is just there as a build-time dependency vs. a runtime dependency, since the build-time src dependencies are tarred up. Disadvantages are: 1. It takes slightly longer to untar at the start of a build. As currently implemented, this attaches the compacted vendor.tar.gz feature as a rider on `verifyCargoDeps`, since both of them are relatively newly implemented behavior that change the `cargoSha256`. If this PR is accepted, I will push forward the remaining rust packages with a series of treewide PRs to update the `cargoSha256`s.
2020-01-12 08:21:23 -08:00
cargoSha256 = "1a6svl89dcdb5fpvs2i32i6agyhl0sx7kkkw70rqr17fyzl5psai";
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
nix-du: 0.2.0 -> 0.3.0
2018-11-03 03:08:23 -07:00
doCheck = true;
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
checkInputs = [ graphviz ];
buildInputs = [
boost
nix
nix-du: 0.2.0 -> 0.3.0
2018-11-03 03:08:23 -07:00
] ++ stdenv.lib.optional stdenv.isDarwin darwin.apple_sdk.frameworks.Security;
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
meta = with stdenv.lib; {
description = "A tool to determine which gc-roots take space in your nix store";
homepage = https://github.com/symphorien/nix-du;
license = licenses.lgpl3;
maintainers = [ maintainers.symphorien ];
nix-du: 0.1.2 -> 0.2.0
2018-06-22 12:39:55 -07:00
platforms = platforms.unix;
nix-du: init at 0.1.1
2018-05-21 13:42:35 -07:00
};
}