apenwarr-redo/t/deps/basic/default.out.do

redo-ifchange $2.in
echo $$
echo $$ >>$2.log
Change definitions of $1,$2,$3 to match djb's redo. If you use "redo --old-args", it will switch back to the old (apenwarr-style) arguments for now, to give you time to update your .do scripts. This option will go away eventually. Note: minimal/do doesn't understand the --old-args option. If you're using minimal/do in your project, keep using the old one until you update your use of $1/$2, and then update to the new one. apenwarr-style default.o.do: $1 foo $2 .o $3 whatever.tmp djb-style default.o.do: $1 foo.o $2 foo $3 whatever.tmp apenwarr-style foo.o.do: $1 foo.o $2 "" $3 whatever.tmp djb-style foo.o.do: $1 foo.o $2 foo.o (I think?) $3 whatever.tmp 2011-12-31 02:45:38 -05:00			`redo-ifchange $2.in`
Add t/deps/basic, to test basic autodependency behaviour. Unfortunately it failed before the previous patch, so that's why this test is needed :( The test is a little ugly, because the bug I'm testing for didn't happen except if you ran 'redo' two times in a row, not two times inside the same redo session. That's because dependency caching inside the one session prevents the accidental rebuild. 2010-11-22 22:44:08 -08:00			`echo $$`
Change definitions of $1,$2,$3 to match djb's redo. If you use "redo --old-args", it will switch back to the old (apenwarr-style) arguments for now, to give you time to update your .do scripts. This option will go away eventually. Note: minimal/do doesn't understand the --old-args option. If you're using minimal/do in your project, keep using the old one until you update your use of $1/$2, and then update to the new one. apenwarr-style default.o.do: $1 foo $2 .o $3 whatever.tmp djb-style default.o.do: $1 foo.o $2 foo $3 whatever.tmp apenwarr-style foo.o.do: $1 foo.o $2 "" $3 whatever.tmp djb-style foo.o.do: $1 foo.o $2 foo.o (I think?) $3 whatever.tmp 2011-12-31 02:45:38 -05:00			`echo $$ >>$2.log`