Your message dated Mon, 21 Nov 2022 17:25:33 +0100 with message-id <[email protected]> and subject line Re: pd-lib-builder: provide a dh-sequence-pdlibbuilder has caused the Debian Bug report #1016709, regarding pd-lib-builder: provide a dh-sequence-pdlibbuilder to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1016709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016709 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: pd-lib-builder Version: 0.6.0-1 Severity: wishlist Many pd-externals use pd-lib-builder, and the d/rules look all very similar. It would be great if we could use dh to remove the duplicate work. 1. check if the make-based build system actually uses Makefile.pdlibbuilder 2. add 'PDLIBBUILDER_DIR=/usr/share/pd-lib-builder/ prefix=/usr pkglibdir=$(pkglibdir)' to the dh_auto_(clean|build|test|install) invocations 3. autofix permissions of pd-externals 4. possibly remove the extraneous LICENSE.txt files that come with Pd Also, once we have puredata64 in Debian, this would: - check which binary package variants are built ('pd-*' vs 'pd64-*) - automatically build both package kinds (if so requested), using different flags And there should be something like ${Pd:Depends} and ${Pd64:Depends} check out the dh-sequence-kf5 how to switch the dh-buildsystem via a sequence
--- End Message ---
--- Begin Message --- The src:dh-puredata package (that ships a dh-puredata binary package providing dh-sequence-pdlibbuilder) has entered Debian.So we no longer need to provide this via pd-lib-builder. gfmadsr IOhannes
--- End Message ---
