The difference between this and svnsync is that svnsync, from what I
understand, will mirror a repository from one svn server to another.
Svn2ftp is designed to work more like a controlled export. It doesn't
replicate the repository, just the head revision of the repository. And
it works over FTP, which I believe is different as well.
A good example of where this might be useful could be a large website in
a subversion repository, where once a change is committed needs to show
up on a remote server for preview.
Thanks for your response. Let me know what you think.
Karl Fogel wrote:
> Thanks for posting the script.
> Normally we include things like this in the contrib/ area. But in
> this case, what is its advantage over the 'svnsync' functionality now
> present in Subversion? I think that might do exactly what this script
> Daniel Falk <email@example.com> writes:
>> I have written a python script that I have found very useful for some
>> of my own repositories and would like to contribute it to the
>> community. I am attaching it. Since it is a script I hope it doesn't
>> get blocked.
>> My script is called svn2ftp.py and it will ftp changed files,
>> directories and deletions between revisions, using svn diff
>> --summarize to know what to sync. It holds onto the last successful
>> sync's revision number so it will always sync the correct stuff even
>> if it fails for some reason.
>> I wrote this to work on my Linux system. I don't know if it will work
>> on other platforms yet. It requires both pysvn and python subversion
>> bindings currently. I don't know whether it can be trimmed down to
>> only having one of these dependencies. Hopefully someone else knows.
>> This is my first time writing a python script, so I don't expect that
>> I did everything right. Which brings up a question. How are these
>> contributed scripts maintained? Are they made part of the main
>> subversion repository, which developers can submit patches to?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Aug 17 02:56:42 2007