On Sun, Nov 06, 2005 at 05:14:05PM -0600, Peter Samuelson wrote:
[Roland Stigge]
It would also be possible to return the differences-found state via a
return/exit value of the script. But that would diverge from common
practice (see e.g., diff(1)).
Heh - did you read diff(1)? diff
Hi,
Peter Samuelson wrote:
It would also be possible to return the differences-found state via a
return/exit value of the script. But that would diverge from common
practice (see e.g., diff(1)).
Heh - did you read diff(1)?
Well, not lately. :) But the manpage actually doesn't mention this
Julian Gilbey wrote:
I prefer the --quiet option, so will go with that (principle of least
surprise). In the case of debdiff, I'm not sure what the exit code
would mean: would it mean that the file lists are different, that the
control files are different, that there was some difference or
Package: devscripts
Version: 2.9.8
Severity: wishlist
Tags: patch
Hi,
in order to use debdiff in scripts, I would need it to let me evaluate
the result of the outcome (differences found or not). This is currently
not easily possible except employing some heuristics by parsing the
output.
I
[Roland Stigge]
It would also be possible to return the differences-found state via a
return/exit value of the script. But that would diverge from common
practice (see e.g., diff(1)).
Heh - did you read diff(1)? diff *does* in fact return 1 iff any
differences are found. So does cmp. grep
5 matches
Mail list logo
