6a800927bb
The pybrial package is a bit awkward. It doesn't have its own top-level attribute, since it has a cyclic dependency with sage. That's one of the reasons why it rarely gets updated. Its distributed along with brial, so its best to keep the versions synchronized. The easiest way to do this is to just re-use the source of brial.
25 lines
710 B
Nix
25 lines
710 B
Nix
{ stdenv
|
|
, fetchFromGitHub
|
|
, buildPythonPackage
|
|
, brial
|
|
}:
|
|
# This has a cyclic dependency with sage. I don't include sage in the
|
|
# buildInputs and let python figure it out at runtime. Because of this,
|
|
# I don't include the package in the main nipxkgs tree. It wouldn't be useful
|
|
# outside of sage anyways (as you could just directly depend on sage and use
|
|
# it).
|
|
buildPythonPackage rec {
|
|
pname = "pyBRiAl";
|
|
version = brial.version;
|
|
|
|
# included with BRiAl source
|
|
src = brial.src;
|
|
|
|
sourceRoot = "source/sage-brial";
|
|
|
|
meta = with stdenv.lib; {
|
|
description = "python implementation of BRiAl";
|
|
license = licenses.gpl2;
|
|
maintainers = with maintainers; [ timokau ];
|
|
};
|
|
}
|