3 commits

Author	SHA1	Message	Date
Avery Pennarun	7822f5a5bb	t/*: rearrange tests into numbered directories. ... It was getting way too ad-hoc in there. Let's reorganize the tests so that there's a good, obvious, suggested sequence to run them in.	2012-02-08 01:56:50 -05:00
Jimmy	4a296d676c	t/defaults-nested/clean fails on MacOS X. ... It seems on OSX find behaves differently (probably from linux): jtang@exia:~/develop/redo $ make clean ./redo clean redo clean redo t/clean redo t/example/clean redo t/curse/clean redo t/deps/clean redo t/deps/basic/clean redo t/deps/dirtest/clean redo t/space dir/clean redo t/stamp/clean redo t/defaults-flat/clean redo t/defaults-nested/clean find: illegal option -- n find: illegal option -- a find: illegal option -- m find: illegal option -- e find: *~: No such file or directory redo t/defaults-nested/clean: exit code 1 redo t/clean: exit code 1 redo clean: exit code 1 make: *** [clean] Error 1 This fixes it for me.	2011-01-18 00:48:51 -08:00
Avery Pennarun	0dcc3f61b6	Search parent directories for default*.do. ... Previously, we would only search for default*.do in the same directory in the target; now we search parent directories as well. Let's say we're in a/b/ and trying to build foo.o. If we find ../../default.o.do, then we'll run cd ../..; sh default.o.do a/b/foo .o $TMPNAME In other words, we still always chdir to the same directory as the .do file. But now $1 might have a path in it, not just a basename.	2010-12-19 05:58:49 -08:00