apenwarr-redo/t/makedir2.do

rm -f makedir.log
redo makedir
touch makedir/outfile
./flush-cache
redo-ifchange makedir
COUNT=$(wc -l <makedir.log)
[ "$COUNT" -eq 1 ] || exit 99
Remove special case for "dirname" -> "dirname/all" It actually decreases readability of the .do files - by not making it explicit when you're going into a subdir. Plus it adds ambiguity: what if there's a dirname.do and a dirname/all? We could resolve the ambiguity if we wanted, but that adds more code, while taking out this special case makes less code and improves readability. I think it's the right way to go. 2010-11-24 02:48:27 -08:00			`rm -f makedir.log`
			`redo makedir`
			`touch makedir/outfile`
Rename flush-cache.py to flush-cache, and rearrange the code a bit. It was working fine, but the style wasn't exactly the way I like it, because I'm unnecessarily picky. :) Also, removed the file extension since we should probably learn from the fact that it's already been rewritten once from one language to another. Who knows, maybe it will be again someday. 2011-02-23 01:24:48 -08:00			`./flush-cache`
Remove special case for "dirname" -> "dirname/all" It actually decreases readability of the .do files - by not making it explicit when you're going into a subdir. Plus it adds ambiguity: what if there's a dirname.do and a dirname/all? We could resolve the ambiguity if we wanted, but that adds more code, while taking out this special case makes less code and improves readability. I think it's the right way to go. 2010-11-24 02:48:27 -08:00			`redo-ifchange makedir`
			`COUNT=$(wc -l <makedir.log)`
Fix tests on MacOS. This comes down to the lack of a 'seq' command (what?!) and the fact that BSD "wc -l" returns extra whitespace, while the GNU version doesn't. We should be using numeric comparisons instead of string comparisons, and then it's ok. 2010-12-12 05:38:30 -08:00			`[ "$COUNT" -eq 1 ] \|\| exit 99`