apenwarr-redo/t/silencetest.do

echo 'echo hello' >silence.do
redo silence
[ -e silence ] || exit 55
echo 'true' >silence.do
redo silence
. ./skip-if-minimal-do.sh
[ ! -e silence ] || exit 66
rm -f silence.do
$3 and stdout no longer refer to the same file. This is slightly inelegant, as the old style echo foo echo blah chmod a+x $3 doesn't work anymore; the stuff you wrote to stdout didn't end up in $3. You can rewrite it as: exec >$3 echo foo echo blah chmod a+x $3 Anyway, it's better this way, because now we can tell the difference between a zero-length $3 and a nonexistent one. A .do script can thus produce either one and we'll either delete the target or move the empty $3 to replace it, whichever is right. As a bonus, this simplifies our detection of whether you did something weird with overlapping changes to stdout and $3. 2010-12-11 00:29:04 -08:00			`echo 'echo hello' >silence.do`
			`redo silence`
			`[ -e silence ] \|\| exit 55`
			`echo 'true' >silence.do`
			`redo silence`
Disable the tests that don't work with minimal/do. ...only when running under minimal/do, of course. The tests in question mostly fail because they're testing particular dependency-related behaviour, and minimal/do doesn't support dependencies, so naturally it doesn't work. 2010-12-11 20:54:46 -08:00			`. ./skip-if-minimal-do.sh`
$3 and stdout no longer refer to the same file. This is slightly inelegant, as the old style echo foo echo blah chmod a+x $3 doesn't work anymore; the stuff you wrote to stdout didn't end up in $3. You can rewrite it as: exec >$3 echo foo echo blah chmod a+x $3 Anyway, it's better this way, because now we can tell the difference between a zero-length $3 and a nonexistent one. A .do script can thus produce either one and we'll either delete the target or move the empty $3 to replace it, whichever is right. As a bonus, this simplifies our detection of whether you did something weird with overlapping changes to stdout and $3. 2010-12-11 00:29:04 -08:00			`[ ! -e silence ] \|\| exit 66`
			`rm -f silence.do`