On Mar 10, 2011, at 10:53 PM, Jakub Wilk wrote: >* Ludovic Rousseau <ludovic.rousseau@gmail.com>, 2011-03-10, 21:41: >>>>My package provides a binary extension so must be compiled for each >>>supported Python versions: 2.5 and 2.6 as of now. >>> >>>...your new debian/rules does *not* compile extensions for all >>supported versions. (The old one did.) >> >>And dh is not (yet) smart enough to do that for me? >The upstream tarball contains both setup.py and Makefile. In such a case dh >uses Makefile-based build system. And then, it cannot possibly know that the >Makefile has anything to do with Python. Passing >--buildsystem=python_distutils to dh might do the trick. I think it does. I'd like to change that so that it preferred the setup.py instead of the Makefile (by default), but don't know how controversial that would be. -Barry
Attachment:
signature.asc
Description: PGP signature