Eric Kow <[EMAIL PROTECTED]> writes: >> +execTests :: TestKind -> String -> IO () >> +execTests k fmt = do >> + copyFile "dist/build/darcs/darcs" "darcs" > > Hmm, I guess this makes sense if we're going to keep the Makefile > around for a while
Please add a comment to the file in question to that effect, so we can easily see *why* that code is there, and remove it when the makefile goes away. >> + rmRf dir > > I don't think the Makefile does this, btw... (which is not to say > that we should slavishly follow the makefile...) In general, Make will leave both intermediary and "final" targets around; only if you run "make clean" or some variation will any generated files be deleted. There's one exception: sometimes make will be able to determine categorically that a target is an intermediary, and remove it for you. This seems to happen more if you use old-style .c.o: instead of %.o: %.c targets. Also, some historically some Darcs targets have included cleanup in phony targets instead of in clean, which is a Bad Thing because if the build script crashes, the intermediaries will be left around and NOT cleaned up by "make clean" (or a variant). _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
