Howdy Barry, On 15-Jan-2014, Ben Finney wrote: > Migrate the packaging for ‘python-coverage’ to take advantage of > simplifications from “pybuild”.
(Including the bug report this time. If you're interested, please subscribe to this bug report <URL:http://www.debian.org/Bugs/Developer#subscribe>. I will use it to track the migration to “pybuild” for this package.) The existing ‘debian/rules’ invokes ‘dh install’ separately for debug and other packages: ===== install: build dh $@ --with python2,python3 --buildsystem=pybuild \ --package ${python2_debug_package_name} \ --package ${python3_debug_package_name} dh $@ --with python2,python3 --buildsystem=pybuild \ $(foreach exclude_part,${debug_object_exclude}, \ --exclude ${exclude_part}) ===== This is because we must install some specific ‘usr/lib/…/coverage/’ files for the debug packages, and must install everything *else* from ‘usr/lib/…/coverage/’ for the library packages. So we must exclude the debug objects from the non-debug packages. How can this be simplified with “pybuild”, in particular its “{package}” placeholder? Without specifying individual package names, I can't see how to achieve the same effect as above. -- \ “A lie can be told in a few words. Debunking that lie can take | `\ pages. That is why my book… is five hundred pages long.” —Chris | _o__) Rodda, 2011-05-05 | Ben Finney <b...@benfinney.id.au> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
