nixpkgs/pkgs/build-support/fetchbower/default.nix

{ stdenv, fetch-bower, git }: name: version: target: outputHash: stdenv.mkDerivation {
  name = "${name}-${version}";
  buildCommand = ''
    out=$PWD/out fetch-bower ${name} ${version} ${target}
    cp -R out $out
  '';
  outputHashMode = "recursive";
  outputHashAlgo = "sha256";
  inherit outputHash;
  buildInputs = [git fetch-bower];
}
Add fetchbower function to go along with bower2nix Signed-off-by: Shea Levy <shea@shealevy.com> 2014-01-06 05:20:22 -08:00			`{ stdenv, fetch-bower, git }: name: version: target: outputHash: stdenv.mkDerivation {`
			`name = "${name}-${version}";`
Make fetchBower a bit more like a normal mkDerivation, which is easier to test. Also, in some cases, the result of fetchBower is different depending on the value of $out. For now, it seems that it works best if using a local output directory before copying to $out. (cherry picked from commit aa4c6b027163abe0891f9ad438899f9679298a64) 2015-07-16 07:35:31 -07:00			`buildCommand = ''`
			`out=$PWD/out fetch-bower ${name} ${version} ${target}`
			`cp -R out $out`
			`'';`
Add fetchbower function to go along with bower2nix Signed-off-by: Shea Levy <shea@shealevy.com> 2014-01-06 05:20:22 -08:00			`outputHashMode = "recursive";`
			`outputHashAlgo = "sha256";`
			`inherit outputHash;`
Make fetchBower a bit more like a normal mkDerivation, which is easier to test. Also, in some cases, the result of fetchBower is different depending on the value of $out. For now, it seems that it works best if using a local output directory before copying to $out. (cherry picked from commit aa4c6b027163abe0891f9ad438899f9679298a64) 2015-07-16 07:35:31 -07:00			`buildInputs = [git fetch-bower];`
Add fetchbower function to go along with bower2nix Signed-off-by: Shea Levy <shea@shealevy.com> 2014-01-06 05:20:22 -08:00			`}`