Hi, > > > 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.
Looking at the code, I'm a bit confused. It looks like this: patch: patch-stamp (well, ${DPATCH_STAMPFN}) patch-stamp: XX XX So, if patch is .PHONY, patch-stamp is a real file, depending on 'patch' should do the right thing (only be invoked if patch-stamp does not exist), and depending on patch-stamp shouldn't be necessary. At least, this is the intention. Could you give me a testcase / log ? regards, junichi -- [EMAIL PROTECTED],debian.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]