On 13/10/2024 23:27, Bill Allombert wrote:
Hello Debian Science,
I am looking at xpython as an example of packaging a xeus kernel.
It defines 4 packages:
Package: xeus-python-dev
Package: libxeus-python0
Package: xpython
Package: python3-xeus-python-shell
Is libxeus-python0 / xeus-python-dev really needed ? Maybe this one is a
special case, but in general I would expect xpython and
python3-xeus-python-shell to be the only ones used.
Possibly not; I don't remember seeing a CMAKE option to only build a
binary when I originally packaged it - either because it didn't exist
then or I just didn't spot it. Building only a binary seems quite
reasonable, I can't see there is much likelihood of the dev package or
private library being useful.
If binary packages are being changed, it might also make sense to build
a versioned xpython package, so eg, when python3.12 and 3.13 are both
supported then both xpython3.12 and 3.13 are built an xpython is a
symlink to the default.
There is even an cmake option to disable building the shared library:
OPTION(XPYT_BUILD_SHARED "Split xpython build into executable and library" ON)
Cheers,
