Frederik Rietdijk 22aef72ff1 python: get rid of msgpack-python, fixes #48864
We already have msgpack, which is the same. Building a Python env with
`spacy` resulted in a collision between an `.so` provided through both
`msgpack` and `msgpack-python`.

I don't know why `transitional = True` was set. These kind of things
should be documented!
2019-09-29 11:01:58 +02:00

40 lines
1.2 KiB
Nix

{ stdenv, fetchFromGitHub, python2Packages, openssl }:
python2Packages.buildPythonApplication rec {
pname = "pybitmessage";
version = "0.6.3.2";
src = fetchFromGitHub {
owner = "bitmessage";
repo = "PyBitmessage";
rev = version;
sha256 = "1lmhbpwsqh1v93krlqqhafw2pc3y0qp8zby186yllbph6s8kdp35";
};
propagatedBuildInputs = with python2Packages; [ msgpack pyqt4 numpy pyopencl ] ++ [ openssl ];
preConfigure = ''
# Remove interaction and misleading output
substituteInPlace setup.py \
--replace "nothing = raw_input()" pass \
--replace 'print "It looks like building the package failed.\n" \' pass \
--replace ' "You may be missing a C++ compiler and the OpenSSL headers."' pass
substituteInPlace src/pyelliptic/openssl.py \
--replace "libdir.append(find_library('ssl'))" "libdir.append('${openssl.out}/lib/libssl.so')"
substituteInPlace src/depends.py \
--replace "ctypes.util.find_library('ssl')" "'${openssl.out}/lib/libssl.so'"
'';
meta = with stdenv.lib; {
homepage = https://bitmessage.org/;
description = "The official Bitmessage client";
license = licenses.mit;
maintainers = with maintainers; [ jgillich ];
platforms = with platforms; linux;
};
}