wow -- looks cool -- that already should take a bit of burden away from copy/pasting debian/rules of my packages from one to another
I wonder if it could also "support" (just throwing against the wall to see if anything sticks): 1. -lib packages to ship extensions in separate packages to reduce impact on archives 2. unit-testing against built/installed modules (if some env variable provides the command to be invoked) 3. building/installing sphinx-based documentation + replacing all the java script libraries with symlinks to sytemwide once from the packages wouldn't it make more sense to ship it in a separate package since it is relevant not only for python3? then it would also make possible to provide backport packages Cheers! On Sat, 19 Jan 2013, Piotr Ożarowski wrote: > [debhelper's #538978 and #597105 bugs BCCed] > Hi, > FYI: python3 package in experimental (3.3.0-2) contains pybuild tool > with dh command sequencer integration. > You can build modules/extensions for Python 2.X *and* Python 3.X with > this debian/rules file: > #!/usr/bin/make -f > %: > dh $@ --with python2,python3 --buildsystem=pybuild -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130120001606.gh19...@onerussian.com
