[Pkg-giraffe-discuss] tracking of changes done by Kopano Upstream

Mark Dufour m.dufour at kopano.com
Mon May 7 08:52:46 BST 2018


hi carsten,

> And one more thing, I've seen Kopano upstream is providing Python3
> packages like python3-kopano and python3-mapi which is quite nice. As
> far I can see there is no configure option to enable the build of such
> packages. What do we need to create the content for Python3 ready
> packages? As I've understood configure.ac we need to export PYTHON so
> something like /usr/bin/python3.
> Wouldn't it be better to build all available python versions. And as it
> looks like you just change the Shebang it shouldn't be that difficult to
> do this twice for this.

thanks a lot for all your feedback!

last conference, guido showed me how to do a basic double configure-make for both python2 and 3, and that's what ended up in our packaging.. on my own system, I now usually configure for python3 as follows:

./configure .. PYTHON="python3" PYTHON_CFLAGS="$(pkg-config python3 --cflags)" PYTHON_LIBS="$(pkg-config python3 --libs)"

it sure would be nice and useful if you could see our packaging files/changes!


thanks!
mark.




More information about the Pkg-giraffe-discuss mailing list