nixpkgs/pkgs/build-support/rust/fetchcargo.nix

{ stdenv, cacert, git, rustc, cargo, rustRegistry }:
{ name ? "cargo-deps", src, sha256, cargoUpdateHook ? "" }:

stdenv.mkDerivation {
  name = "${name}-fetch";
  buildInputs = [ rustc cargo git ];
  builder = ./fetch-builder.sh;
  fetcher = ./fetch-cargo-deps;
  inherit src rustRegistry cargoUpdateHook;

  outputHashAlgo = "sha256";
  outputHashMode = "recursive";
  outputHash = sha256;

  SSL_CERT_FILE = "${cacert}/etc/ca-bundle.crt";

  impureEnvVars = [ "http_proxy" "https_proxy" "ftp_proxy" "all_proxy" "no_proxy" ];
  preferLocalBuild = true;
}
Add support for building cargo'ed Rust programs 2014-10-10 14:59:37 +00:00			`{ stdenv, cacert, git, rustc, cargo, rustRegistry }:`
buildRustPackage: Fix Cargo.lock being ignored It turns out that `cargo`, with respect to registry dependencies, was ignoring the package versions locked in `Cargo.lock` because we changed the registry index URL. Therefore, every time `rustRegistry` would be updated, we'd always try to use the latest version available for every dependency and as a result the deps' SHA256 hashes would almost always have to be changed. To fix this, now we do a string substitution in `Cargo.lock` of the `crates.io` registry URL with our URL. This should be safe because our registry is just a copy of the `crates.io` registry at a certain point in time. Since now we don't always use the latest version of every dependency, the build of `cargo` actually started to fail because two of the dependencies specified in its `Cargo.lock` file have build failures. To fix the latter problem, I've added a `cargoUpdateHook` variable that gets ran both when fetching dependencies and just before building the program. The purpose of `cargoUpdateHook` is to do any ad-hoc updating of dependencies necessary to get the package to build. The use of the '--precise' flag is needed so that cargo doesn't try to fetch an even newer version whenever `rustRegistry` is updated (and therefore have to change depsSha256 as a consequence). 2015-04-23 00:43:11 +00:00			`{ name ? "cargo-deps", src, sha256, cargoUpdateHook ? "" }:`
Add support for building cargo'ed Rust programs 2014-10-10 14:59:37 +00:00
			`stdenv.mkDerivation {`
			`name = "${name}-fetch";`
			`buildInputs = [ rustc cargo git ];`
			`builder = ./fetch-builder.sh;`
			`fetcher = ./fetch-cargo-deps;`
buildRustPackage: Fix Cargo.lock being ignored It turns out that `cargo`, with respect to registry dependencies, was ignoring the package versions locked in `Cargo.lock` because we changed the registry index URL. Therefore, every time `rustRegistry` would be updated, we'd always try to use the latest version available for every dependency and as a result the deps' SHA256 hashes would almost always have to be changed. To fix this, now we do a string substitution in `Cargo.lock` of the `crates.io` registry URL with our URL. This should be safe because our registry is just a copy of the `crates.io` registry at a certain point in time. Since now we don't always use the latest version of every dependency, the build of `cargo` actually started to fail because two of the dependencies specified in its `Cargo.lock` file have build failures. To fix the latter problem, I've added a `cargoUpdateHook` variable that gets ran both when fetching dependencies and just before building the program. The purpose of `cargoUpdateHook` is to do any ad-hoc updating of dependencies necessary to get the package to build. The use of the '--precise' flag is needed so that cargo doesn't try to fetch an even newer version whenever `rustRegistry` is updated (and therefore have to change depsSha256 as a consequence). 2015-04-23 00:43:11 +00:00			`inherit src rustRegistry cargoUpdateHook;`
Add support for building cargo'ed Rust programs 2014-10-10 14:59:37 +00:00
			`outputHashAlgo = "sha256";`
			`outputHashMode = "recursive";`
			`outputHash = sha256;`

			`SSL_CERT_FILE = "${cacert}/etc/ca-bundle.crt";`

			`impureEnvVars = [ "http_proxy" "https_proxy" "ftp_proxy" "all_proxy" "no_proxy" ];`
			`preferLocalBuild = true;`
			`}`