On Tue, Jun 09, 2026 at 09:01:41PM +0200, Gard Spreemann wrote:
I maintain python3-gudhi. Recently, upstream has moved to a pybuild-based setup for the Python part of their code (albeit one that in turn invokes CMake). The unusual thing is that prior to building, one has to generate various source trees (from the main source tree) in which the various binary packages will be built. One separate tree is generated for each supported Python version.
What are the differences between these trees? This is not related to your question but may be important for the .deb we want to get. Mainly because normally a python3-foo deb ships only an universal /usr/lib/python3/dist-packages/foo dir, maybe with per-interpreter .so files inside, but with all other files shared between interpreters.
I can't seem to figure out how to have the dh-python sequencer invoke the usual pybuild steps on *each* of these generated source directories separately, and restricting to one particular Python version for each one.
pybuild is a debhelper build system so I assume you can simply call dh_auto_* manually for each dir.
-- WBR, wRAR
signature.asc
Description: PGP signature
