Justin Humm b66ef28841 buildRustPackage, fetchcargo: optionally use vendor config from cargo-vendor ... By setting useRealVendorConfig explicitly to true, the actual (slightly modified) config generated by cargo-vendor is used. This solves a problem, where the static vendor config in pkgs/build-support/rust/default.nix would not sufficiently replace all crates Cargo is looking for. As useRealVendorConfig (and writeVendorConfig in fetchcargo) default to false, there should be no breakage in existing cargoSha256 hashes. Nethertheless, imho using this new feature should become standard. A possible deprecation path could be: - introduce this patch - set useRealVendorConfig explicitly to false whereever cargoSha256 is set but migration is not wanted yet. - after some time, let writeVendorConfig default to true - when useRealVendorConfig is true everywhere cargoSha256 is set and enough time is passed, `assert cargoVendorDir == null -> useRealVendorConfig;`, remove old behaviour - after some time, remove all appearences of useRealVendorConfig and the parameter itself		2018-09-11 23:44:14 +02:00
..
manual	buildRustPackage, fetchcargo: optionally use vendor config from cargo-vendor	2018-09-11 23:44:14 +02:00
varlistentry-fixer.rb	doc: Adds xml fixing script. (see previous and next commits)	2018-05-31 21:02:15 -04:00
xmlformat.conf	doc: Adds rule to xmlformat to help keep spacing right.	2018-05-31 21:02:15 -04:00