forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add a redo-always command: it adds an "always dirty" dependency to your target.

Browse source 
This is mostly useless except when combined with redo-stamp... I think.
This commit is contained in:
Avery Pennarun 2010-12-11 07:02:45 -08:00
commit 0da5c7c082
10 changed files with 45 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
t/stamp/stamptest.do
View file

@ -7,6 +7,7 @@ redo stampy
# stampy already exists, so we won't generate it a second time, even though
# usestamp depends on it.
../flush-cache.sh
redo-ifchange usestamp
[ "$(wc -l <stampy.log)" -eq 1 ] || exit 21
[ "$(wc -l <usestamp.log)" -eq 1 ] || exit 12
@ -17,6 +18,7 @@ redo stampy
[ "$(wc -l <usestamp.log)" -eq 1 ] || exit 32
# same as above: stampy is already up-to-date, so it won't be redone.
../flush-cache.sh
redo-ifchange usestamp
[ "$(wc -l <stampy.log)" -eq 2 ] || exit 41
[ "$(wc -l <usestamp.log)" -eq 1 ] || exit 42