ae4a1a485a
If a Python package does not come with either `format` or `pyproject` we consider it a setuptools build, that calls `setup.py` directly, which is deprecated. This change, as a first step, migrates a large chunk of these packages to set setuptools as their explicit format This is so we can unify the problem space for the next step of the migration.
33 lines
674 B
Nix
33 lines
674 B
Nix
{
|
|
lib,
|
|
buildPythonPackage,
|
|
sage-src,
|
|
cython,
|
|
jinja2,
|
|
pkgconfig, # the python module, not the pkg-config alias
|
|
}:
|
|
|
|
buildPythonPackage rec {
|
|
version = src.version;
|
|
format = "setuptools";
|
|
pname = "sage-setup";
|
|
src = sage-src;
|
|
|
|
nativeBuildInputs = [ cython ];
|
|
buildInputs = [ pkgconfig ];
|
|
propagatedBuildInputs = [ jinja2 ];
|
|
|
|
preBuild = ''
|
|
cd pkgs/sage-setup
|
|
'';
|
|
|
|
doCheck = false; # sagelib depends on sage-setup, but sage-setup's tests depend on sagelib
|
|
|
|
meta = with lib; {
|
|
description = "Build system of the Sage library";
|
|
homepage = "https://www.sagemath.org";
|
|
license = licenses.gpl2Plus;
|
|
teams = [ teams.sage ];
|
|
};
|
|
}
|