apenwarr-redo/clean.do

if [ -e .do_built ]; then
	while read x; do
		rm -f "$x"
	done <.do_built
fi
[ -z "$DO_BUILT" ] && rm -rf .do_built .do_built.dir
redo t/clean Documentation/clean
rm -f *~ .*~ */*~ */.*~ *.pyc install.wrapper
rm -rf t/.redo redo-sh
find . -name '*.tmp' -exec rm -fv {} \;
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			`if [ -e .do_built ]; then`
			`while read x; do`
			`rm -f "$x"`
			`done <.do_built`
			`fi`
minimal/do: make redo-ifchange (etc) into subprograms in a temp dir. Using aliases for them was cute, but it didn't work with things like: find -name '*.c' \| xargs redo-ifchange since xargs doesn't know about aliases. 2010-12-11 21:47:55 -08:00			`[ -z "$DO_BUILT" ] && rm -rf .do_built .do_built.dir`
Add a bunch of manpages. 2010-12-12 01:59:26 -08:00			`redo t/clean Documentation/clean`
Add an 'install' target. (usable as 'make install' or 'redo install', of course) 2010-12-12 02:33:08 -08:00			`rm -f ~ .~ /~ /.~ *.pyc install.wrapper`
Automatically select a good shell instead of relying on /bin/sh. This includes a fairly detailed test of various known shell bugs from the autoconf docs. The idea here is that if redo works on your system, you should be able to rely on a good shell to run your .do files; you shouldn't have to work around zillions of bugs like autoconf does. 2010-12-21 04:19:50 -08:00			`rm -rf t/.redo redo-sh`
Don't rely on GNU find behaviour in clean.do. 2010-12-17 11:40:42 -08:00			`find . -name '*.tmp' -exec rm -fv {} \;`