> So it seems like the *only* thing we're in potential disagreement
> about is whether we should automatically invoke this target *iff*
> there's a solid way to automatically determine when doing so would be
> appropriate.
Hmm. As a less automagic alternative, perhaps I could just arrange it
so that we just detect when the debian/autofiles.dpatch is out of date
and then print a suitable error message, rather than trying to update
it, i.e.
$ fakeroot debian/rules binary
...
ERROR: debian/patches/autofiles.dpatch out of date with respect to
other patches. Please update it via "debian/rules update-autofiles-dpatch"
and try again.
$
The test would be handled via md5sum as previously described.
Rob Browning <email address hidden> writes:
> So it seems like the *only* thing we're in potential disagreement
> about is whether we should automatically invoke this target *iff*
> there's a solid way to automatically determine when doing so would be
> appropriate.
Hmm. As a less automagic alternative, perhaps I could just arrange it autofiles. dpatch is out of date
so that we just detect when the debian/
and then print a suitable error message, rather than trying to update
it, i.e.
$ fakeroot debian/rules binary patches/ autofiles. dpatch out of date with respect to autofiles- dpatch"
...
ERROR: debian/
other patches. Please update it via "debian/rules update-
and try again.
$
The test would be handled via md5sum as previously described.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4