apenwarr-redo/clean.do

exec >&2
rm -rf t/.redo redo-sh
if [ -e .do_built ]; then
	while read x; do
		[ -d "$x" ] || rm -f "$x"
	done <.do_built
fi
[ -z "$DO_BUILT" ] && rm -rf .do_built .do_built.dir
rm -rf minimal/.do_built minimal/.do_built.dir website
redo t/clean Documentation/clean version/clean
rm -f *~ .*~ */*~ */.*~ *.pyc install.wrapper
find . -name '*.tmp' -exec rm -fv {} \;
find . -name '*.did' -exec rm -fv {} \;
minimal/do: didn't work correctly with multi-level auto dir creation. If we tried to build target a/b/c/d and a/b/c didn't exist yet, we would correctly name the temp file something like a__b/c__d.tmp. But if a/b didn't exist yet, we named the temp file a/b__c/d.tmp, which didn't work. Instead, name it a/b__c__d.tmp as expected. 2018-11-02 04:17:27 -04:00			`exec >&2`
minimal/do: use ".did" stamp files instead of empty target files. If all.do runs and creates no output, we shouldn't create a file called 'all', but we should remember that 'all' has been run successfully. We do this by creating 'all.did' during the build. Since minimal/do always just wipes everything out every time it runs, we can safely remove the .did files after minimal/do terminates, so this doesn't clutter things too much in normal use. This fixes some edge cases, particularly that 'minimal/do clean' no longer leaves stupid files named "clean" lying around, and the redo-sh directory can now be rebuilt correctly since we rebuild it as long as redo-sh.did doesn't exist. (We don't want to "rm -rf redo-sh" because it makes me nervous.) 2011-01-01 03:42:35 -08:00			`rm -rf t/.redo redo-sh`
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`
Don't crash on targets in directories that don't exist yet. The reason we'd crash is that we tried to pre-create a file called $target.redo.tmp, which wouldn't work because the directory containing $target didn't exist. We now try to generate a smarter filename by using the innermost directory of target that does exist. It's a little messy, but the idea is to make sure we won't have to rename() across a filesystem boundary if, for example, there's a mounted filesystem in the middle of the hierarchy somewhere. 2011-03-22 22:09:56 -07:00			`[ -d "$x" ] \|\| rm -f "$x"`
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			`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`
redo-log: add man page. 2018-11-19 19:28:25 -05:00			`rm -rf minimal/.do_built minimal/.do_built.dir website`
Generate redo version codes in Documentation/*.1 automatically. We have to go through some pretty scary gyrations to extract this information from git, but it can be done. This works with both tarballs generated by 'git archive', or with your local git repo. (Requested by 'David' on the mailing list.) 2011-01-17 23:00:20 -08:00			`redo t/clean Documentation/clean version/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`
Don't rely on GNU find behaviour in clean.do. 2010-12-17 11:40:42 -08:00			`find . -name '*.tmp' -exec rm -fv {} \;`
{ood,sources,targets}: fix relative paths; turn missing targets into sources. When we check dependencies and a previously-is_generated dependency existed before, but no longer does, forget that it was is_generated. This slightly improves the situation where as a project evolves, a file that used to be a target gets removed, and then later is re-added as a static source file. (It doesn't fix the other variant, where a file is changed from target to source in a single atomic change, and is never missing. That one will be trickier to handle.) While adding a test for this behaviour, I discovered that redo-sources, redo-targets, and redo-ood were reporting their output relative to STARTDIR instead of relative to $PWD, so fix that too. 2018-11-23 18:20:32 -05:00			`find . -name '*.did' -exec rm -fv {} \;`