On Wed, Jun 20, 2007 at 04:22:57AM +0900, Junichi Uekawa wrote: > 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. > > Where could it be documented as to be effective?
The very nice "SIDE EFFECTS" section of the dpatch.make manpage? :) -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
