Daniël de Kok b3969f3ad7 rustPlatform.buildRustPackage: support direct use of Cargo.lock ... This change introduces the cargoLock argument to buildRustPackage, which can be used in place of cargo{Sha256,Hash} or cargoVendorDir. It uses the importCargoLock function to build the vendor directory. Differences compared to cargo{Sha256,Hash}: - Requires a Cargo.lock file. - Does not require a Cargo hash. - Retrieves all dependencies as fixed-output derivations. This makes buildRustPackage much easier to use as part of a Rust project, since it does not require updating cargo{Sha256,Hash} for every change to the lock file.		2021-05-28 08:01:28 +02:00
..
build-rust-crate	build-rust-crate: disable incremental builds	2021-04-08 10:45:56 +02:00
hooks	cargo/hooks: allow hooks to be disabled	2021-03-08 19:17:03 +01:00
patch-registry-deps
sysroot	add sysroot lockfile update script then run it	2020-10-17 01:34:51 -07:00
cargo-vendor-normalise.py
carnix.nix
crates-io.nix
default-crate-overrides.nix	treewide: stdenv.lib -> lib	2021-01-24 01:49:49 +01:00
default.nix	rustPlatform.buildRustPackage: support direct use of Cargo.lock	2021-05-28 08:01:28 +02:00
fetchcargo-default-config.toml
fetchCargoTarball.nix	fetchCargoTarball: set default sourceRoot to the empty string	2021-02-11 20:00:13 +01:00
fetchcrate.nix	fetchCrate: accept pname besides crateName	2020-08-28 08:34:22 +02:00
import-cargo-lock.nix	rustPlatform.importCargoLock: init	2021-05-28 08:01:25 +02:00