[Ben Finney, 2014-01-31] > Piotr Ożarowski <pi...@debian.org> writes: > > add python-all-dbg or python3-all-dbg to Build-Depends, is that simple > > enough? :) > > It's a bit magical and AFAICT undocumented.
`man pybuild` or http://anonscm.debian.org/gitweb/?p=dh-python/dh-python.git;a=blob;f=pybuild.rst#l19 > It also behaves differently from ‘dh_python3’: the debug library files > are not in ‘usr/lib/python3/’, but ‘usr/lib/python3.3/’. Why the > difference? pybuild DOESN'T replace dh_python{2,3}. It builds/installs files in locations where dh_python* (or dh_pysupport) expects them. It installs to /usr/lib/python3.3/ not only for -dbg interpreters, it does the same for regular ones as well. dh_python* later moves these files to /usr/lib/python3/ - that's a hack which allows dh_python* to recognize interpreter version for which given extension was built (this information is needed to generate appropriate dependencies and to add correct multiarch tuples) > What about the ‘dh_install’ step? How should we specify the non-debug > packages to omit the debug library files, and the debug packages to > include those library files? By the usual ‘foo.install’ and > ‘foo-dbg.install’ configuration files? yes, or simply export PYBUILD_NAME and pybuild will set DESTDIR for you (no need for .install files) PS did I mention that pybuild doesn't replace dh_python2 nor dh_python3? (duno why but a lot of people assume that pybuild is yet another dh_* helper - it's not, it's dh *buildsystem*) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- 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/20140131120059.gx4...@sts0.p1otr.com