Date: Sat, 19 Nov 2022 15:25:30 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 267866] net-p2p/py-libtorrent-rasterbar: fix python bindings and update to 1.2.18 Message-ID: <bug-267866-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267866 Bug ID: 267866 Summary: net-p2p/py-libtorrent-rasterbar: fix python bindings and update to 1.2.18 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: yuri@freebsd.org Reporter: jocke@gipset.se Flags: maintainer-feedback?(yuri@freebsd.org) Assignee: yuri@freebsd.org Taken from my work on a deluge version bump, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264970. Some problems I could not solve in a nice way: 1. The python bindings were trying to find a file named `libtorrent-rasterbar.so.10.0.0` but in the default build it seems to be na= med `libtorrent-rasterbar.so.1.2.18` (with a symlink `libtorrent-rasterbar.so.1= 0` pointing to it) so I had to construct an additional symlink in the last sta= ges of the build. It would be nice if this could be configured to either create= the symlink through the Jamfile or to have the python binding look for one of t= he existing names. 2. The python binding seems to go in a subdirectory in site-packages which seems to not be supported out of the box with FreeBSD ports system python utils. I am not sure which way is more correct in python/general but in por= ts I had to disable the automatic file detection and explicitly add `${PYTHON_SITELIBDIR}/${PYDISTUTILS_PKGNAME}/__init__${PYTHON_EXT_SUFFIX}.s= o`. The old way of keeping the `.so` file right in the site-packages directory seemed to work automatically. Some more context available here: https://github.com/arvidn/libtorrent/issues/6890#issuecomment-1320873270 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267866-7788>