Open severin-lemaignan opened 2 years ago
A quick work-around might be to use wheel2deb
, I suppose.
Is there a reason you'd prefer the debian packaging rather than just PyPi?
As a note to myself, because I'm using GH Actions to do the packaging I don't actually have the .whl
files locally. Luckily they are hosted on PyPi
We would like to deploy reasonable
on our robots, and we have a strict policy of only distributing deb packages on the robots (as this enables a pretty complex game of dependencies + continuous integration). pypi
is fine for development, of course, but I'll need to package reasonable
as a debian for 'proper' distribution.
Also, it would be nice to have it in the upstream debian/ubuntu repos at some point!
@severin-lemaignan I've finally got my build pipeline working again and I'm taking a look at the Debian packaging. What architecture should I prioritize if I can't get them all working?
great to hear! My target platform is amd64 (on ubuntu 20.04).
Is there a working Debian/Ubuntu package available?
hi! In order to easily depend on
reasonable
, I'd like to package it ondebian
.Packaging
reasonable
as a deb has however proven to be tricky:reasonable
is written in rust, uses maturin to compile the Python bindingspyproject.toml
(that specifymaturin
as build tool).poetry
is used to perform the compilation + pypi distribution.py2dsc
(part ofstdeb
) andpybuild
, part ofdh-python
) do not yet support PEP-517 (on-going work, but not available in ubuntu 20.04, and, based on the code of the plugin, probably not compatible with maturin)debmake
) the debian control + rules, using thisrules
file:-> compiles, but the resulting
.deb
is empty -> need to 'install' the compiledlibreasonable.so
.Do you have any suggestions/ideas to help with it?