Package: dpatch Version: 2.0.21 Severity: minor Consider a standard case of dpkg-buildpackage invoking "build" first and then "binary" next.
Adding a dependancy on "patch" to one's "build" or "configure" (or whatever) target, causes this target to be re-run even when not strictly necessary, during the second invocation. Replacing "patch" with "dpatch-stamp" fixes the issue for me, but is bound to break if dpatch.make changes behavior at some point to do something important in the "patch" target (other than depending on the stamp file). I don't know if it can be fixed easily, other than recommending to depend on "dpatch-stamp" rather than "patch". Either way, I think it should be documented. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) dpatch depends on no packages. Versions of packages dpatch recommends: ii dpkg-dev 1.13.25 package building tools for Debian ii fakeroot 1.5.10 Gives a fake root environment ii patchutils 0.2.31-3 Utilities to work with patches -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
