On 16.10.2007, at 18:31, Eric Kolve wrote:
> > I have uploaded a tar of a copy strategy 'rsync' into this group > Well, it seems that we'll wind up with many many rsync deployment strategies. At least four and still counting. Just search the archives... > The only downside i see to this is that it depends on a rsync > executable. If there is interest in incorporating this into the > project, i could probably create something in pure ruby that would be > rsync-like and accomplish the same thing. I don't think this is a good idea. Actually, I think it is a very bad idea... There are certain features of rsync that are rather hard to implement, e.g. rsync can transfer only the changed parts of files, which comes handy when time stamps are different (but file contents are the same) due to way the scm exports files. Not to mention correct handling of file attributes and weird file types, pipelining of processing and networking, robustness etc... Rsync is a quite clever and well-tested program for transferring files. izidor --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
