Peter Donald wrote: > > ahh - okay. I tend to run a > > gen.sh ; ~/bin/build gump scripts; ~/bin/build myproject
The first two commands should do roughly the same thing, neither should update the .timestamp. But I see the problem: if the timestamps is updated by a cron job, then your private scripts are out of synch. > and then go do some washing and cleaning up ;) So in theory I only need to > run gen.sh once per day (or at least once after the 7am run) and then just > run A much more streamlined approach would be to copy the build.sh and update.sh from your gump/work directory to a well known place. Update ~/bin/build to run from there and optionally update it when done. And then periodically: ~/bin/build gump clean scripts > ~/bin/build gump scripts; ~/bin/build myproject That makes sense since you are heavy into modifying the project definitions at the moment. I typically skip the first step, but it is largely harmless as it will only generate what it needs to anyway. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
