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)? The code can be found at svn://svn.debian.org/svn/pkg-gtkpod/libgpod/trunk Comments and suggestions welcome. Gruesse and thanks for any help in advance, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
