[Bug 267866] net-p2p/py-libtorrent-rasterbar: fix python bindings and update to 1.2.18

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267866

            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=264970.

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 named
`libtorrent-rasterbar.so.1.2.18` (with a symlink `libtorrent-rasterbar.so.10`
pointing to it) so I had to construct an additional symlink in the last stages
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 the
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 ports I
had to disable the automatic file detection and explicitly add
`${PYTHON_SITELIBDIR}/${PYDISTUTILS_PKGNAME}/__init__${PYTHON_EXT_SUFFIX}.so`.
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

-- 
You are receiving this mail because:
You are the assignee for the bug.