On Tue, 16 Nov 2004 09:06:24 -0600, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > In the end the major difference is a philosophical one. What is the > > central piece of the task, the repository or downloading of files. > > > > I guess I'm more on the side of the declarative approach dependencies > > takes, but I do want those additional bells and whistles like MD5 > > checksum validations and timestamp checks if needed. > > I feel similarly. I prefer the declarative approach of <dependencies>,
Me, too :) Ultimately, I think this is more of a usability issue than anything else. So I will continue developing the dependencies task as an external task for now, to let people try it. But I will use feedback from this list and elsewhere to guide it. I suspect it is premature to decide without some real usage. > but would like timestamp checking for latest-like dependencies that get > overwritten (which does need a pseudo-atomic copy-to-tmp+move scheme). Do you think that triggering this based on a version of "latest" makes the most sense, or do we need a separate nested task or boolean flag? I like the version approach except that I hate to make decisions based on a string value. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
