JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
74276caf19
nixpkgs/pkgs/development/python-modules/buildout-nix/default.nix

22 lines
640 B
Nix
Raw Normal View History

Add a patched version of buildout 2.2.0 for development with nix Without this patch buildout will copy eggs from the nix store into the ./eggs directory and then try to compile them. This fails because they are read only. This patch changes the behaviour to create symlinks to eggs available in the nix store instead of copying them, and not to try to compile the eggs in the store. To differentiate this from the default buildout (which may be provided otherwise e.g. as a dependency) the executable is renamed to buildout-nix. This can be used in conjuntion with myEnvFun to create development environments which make use of the python modules available in the store while downloading any additional required eggs. A pleasant side effect is that you can conveniently replace the symlink with a copy for debugging purposes.
2013-08-27 23:26:06 +01:00
{ fetchurl, stdenv, buildPythonPackage }:
buildPythonPackage {
pythonPackages: zc.buildout-nix: 2.5.0 -> 2.5.3
2016-09-29 07:49:27 +01:00
name = "zc.buildout-nix-2.5.3";
Add a patched version of buildout 2.2.0 for development with nix Without this patch buildout will copy eggs from the nix store into the ./eggs directory and then try to compile them. This fails because they are read only. This patch changes the behaviour to create symlinks to eggs available in the nix store instead of copying them, and not to try to compile the eggs in the store. To differentiate this from the default buildout (which may be provided otherwise e.g. as a dependency) the executable is renamed to buildout-nix. This can be used in conjuntion with myEnvFun to create development environments which make use of the python modules available in the store while downloading any additional required eggs. A pleasant side effect is that you can conveniently replace the symlink with a copy for debugging purposes.
2013-08-27 23:26:06 +01:00
src = fetchurl {
pythonPackages: zc.buildout-nix: 2.5.0 -> 2.5.3
2016-09-29 07:49:27 +01:00
url = "https://pypi.python.org/packages/e4/7b/63863f09bec5f5d7b9474209a6d4d3fc1e0bca02ecfb4c17f0cdd7b554b6/zc.buildout-2.5.3.tar.gz";
sha256 = "3e5f3afcc64416604c5efc554c2fa0901b60657e012a710c320e2eb510efcfb9";
Add a patched version of buildout 2.2.0 for development with nix Without this patch buildout will copy eggs from the nix store into the ./eggs directory and then try to compile them. This fails because they are read only. This patch changes the behaviour to create symlinks to eggs available in the nix store instead of copying them, and not to try to compile the eggs in the store. To differentiate this from the default buildout (which may be provided otherwise e.g. as a dependency) the executable is renamed to buildout-nix. This can be used in conjuntion with myEnvFun to create development environments which make use of the python modules available in the store while downloading any additional required eggs. A pleasant side effect is that you can conveniently replace the symlink with a copy for debugging purposes.
2013-08-27 23:26:06 +01:00
};
patches = [ ./nix.patch ];
postInstall = "mv $out/bin/buildout{,-nix}";
meta = {
homepage = "http://www.buildout.org";
description = "A software build and configuration system";
license = stdenv.lib.licenses.zpt21;
maintainers = [ stdenv.lib.maintainers.goibhniu ];
};
}
Reference in New Issue Copy Permalink