GNU `tar' reports a vague `write error' as a result of the broken pipe
caused by the following `grep' finding a successful match. This isn't
useful. In our case, we don't care about this, since either we've found
the file anyway (so we're happy) or we didn't (in which case we'll fail
anyway).
The report, which makes its way to stderr even in quiet mode, is
worrying until you learn to ignore it, at which point it may hide a more
serious problem.
-if ! tar tfz $buildpath/$distdir.tar.gz | grep -q RELEASE; then
+if ! tar tf $buildpath/$distdir.tar.gz 2>/dev/null | grep -q RELEASE; then
fail "missing RELEASE file in distribution"
fi
fail "missing RELEASE file in distribution"
fi