apenwarr-redo/t/chdirtest.do

. ./skip-if-minimal-do.sh

rm -f chdir1
redo chdir2
redo chdir3

./flush-cache
redo-ifchange chdir3

rm -f chdir1
./flush-cache
redo-ifchange chdir3
[ -e chdir1 ] || exit 77

rm -f chdir1
./flush-cache
redo-ifchange chdir3
[ -e chdir1 ] || exit 78
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			`. ./skip-if-minimal-do.sh`

Correctly handle dependencies for "cd somewhere; redo-ifchange somefile" We would build 'somefile' correctly the first time, but we wouldn't attach the dependency on somefile to the right $TARGET, so our target would not auto-rebuild in the future based on somefile. 2010-11-24 03:06:18 -08:00			`rm -f chdir1`
This tests the chdir-related bug from the previous commit. 2010-11-25 06:31:06 -08:00			`redo chdir2`
			`redo chdir3`

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`
This tests the chdir-related bug from the previous commit. 2010-11-25 06:31:06 -08:00			`redo-ifchange chdir3`
Correctly handle dependencies for "cd somewhere; redo-ifchange somefile" We would build 'somefile' correctly the first time, but we wouldn't attach the dependency on somefile to the right $TARGET, so our target would not auto-rebuild in the future based on somefile. 2010-11-24 03:06:18 -08:00
This tests the chdir-related bug from the previous commit. 2010-11-25 06:31:06 -08:00			`rm -f chdir1`
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`
This tests the chdir-related bug from the previous commit. 2010-11-25 06:31:06 -08:00			`redo-ifchange chdir3`
Correctly handle dependencies for "cd somewhere; redo-ifchange somefile" We would build 'somefile' correctly the first time, but we wouldn't attach the dependency on somefile to the right $TARGET, so our target would not auto-rebuild in the future based on somefile. 2010-11-24 03:06:18 -08:00			`[ -e chdir1 ] \|\| exit 77`
This tests the chdir-related bug from the previous commit. 2010-11-25 06:31:06 -08:00
			`rm -f chdir1`
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`
This tests the chdir-related bug from the previous commit. 2010-11-25 06:31:06 -08:00			`redo-ifchange chdir3`
			`[ -e chdir1 ] \|\| exit 78`