Le sam 30 septembre 2006 01:47, Frank Lichtenheld a écrit : > Hi. > > I maintain the libgpod package which also provides python bindings > in the python-gpod package. While preparing a new upstream version > for upload I noticed that upstream changed the build system for > the python bindings so that the patch provided by Raphael Hertzog > to build them according to python policy doesn't work anymore. > Now it seems awful complicated to patch the package again to build > more than one version of the bindings. Which means I would have to go > back to only providing some for the default python version. As far as > I can tell this wouldn't cause much problems since the only rdepends > is using the 2.4 version anyway. > > But maybe someone of you has a good idea to patch the package to make > providing more than one version easy again (given the fact that many > of you have probably seen more than one build system for python > bindings unlike me)? > Or maybe someone would like to point out why only providing a 2.4 > version of the bindings is really a bad idea (e.g. people that might > actually use the package, again unlike me)? with the autotools, to chose the python version you build for, you just need: PYTHON=pythonX.Y ./configure ..... -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgppmHbvbqSau.pgp
Description: PGP signature