Kevin Cox 4499513e54 rust: Allow setting cargoSha256 to null. ... Setting the hash to null is a convenient way to bypass the hash check while developing. It looks like the ability to do this was inadvertently removed while adding vendor directory support. This still checks that the user is explicitly setting the value but allows null as a valid option.		2018-04-07 22:48:55 +01:00
..
cargo-vendor	cargo-vendor: Build from source using carnix	2018-01-18 20:44:42 +09:00
patch-registry-deps	buildRustPackage: don't hardcode /nix/store, use $NIX_STORE	2016-01-12 13:45:11 -05:00
build-rust-crate.nix	buildRustCrate: remove ancient test guards	2018-03-28 09:24:22 +01:00
carnix.nix	BuildRustCrate: more general overrides, and handling the "dylib" crate type (#35171)	2018-02-20 08:55:04 +01:00
default-crate-overrides.nix	tree-wide: autorename gnome packages to use dashes	2018-02-25 17:41:16 +01:00
default.nix	rust: Allow setting cargoSha256 to null.	2018-04-07 22:48:55 +01:00
fetchcargo.nix	build-support/rust: make use of abandoned cargoUpdateHook	2018-02-23 11:17:03 +07:00
fetchcrate.nix	add fetchCrate function to fetch rust crates	2017-12-12 04:58:45 -06:00