Questions regarding upcoming svnsync tool

[Sebastian Schuberth <ss...@gmail.com>]

Hi,

I've looked at the source to svnsync in the 1.4 RC5 download, yet I'm 
not sure whether svnsync will suit our needs.

We have two office locations which are only connected via low-bandwidth 
Internet. Accessing a SVN repository at location A from location B takes 
far too long. So the idea was to set up two repositories, one at each 
location, which are automatically bidirectionally synchronized at each 
commit (not only once a day or something).

Is this something we could archive with svnsync, by calling it from a 
post-commit-hook on each side? Moreover, this only makes sense if the 
committing user does not have to wait until the post-commit-hook 
finishes. Is this possible?

Thanks.

-- 
Sebastian Schuberth

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Questions regarding upcoming svnsync tool

[Garrett Rooney <ro...@electricjellyfish.net>]

On 9/4/06, Sebastian Schuberth <ss...@gmail.com> wrote:
> Hi,
>
> I've looked at the source to svnsync in the 1.4 RC5 download, yet I'm
> not sure whether svnsync will suit our needs.
>
> We have two office locations which are only connected via low-bandwidth
> Internet. Accessing a SVN repository at location A from location B takes
> far too long. So the idea was to set up two repositories, one at each
> location, which are automatically bidirectionally synchronized at each
> commit (not only once a day or something).
>
> Is this something we could archive with svnsync, by calling it from a
> post-commit-hook on each side? Moreover, this only makes sense if the
> committing user does not have to wait until the post-commit-hook
> finishes. Is this possible?

No, it is not.  svnsync is for maintaining read-only mirrors, it has
no ability to do bidirectional syncing like what you're talking about.
 In order to replay commits like that you'd need to do a bunch of
locking to ensure that when a commit is going on in project A nothing
is being changed in project B, and currently there's no way to do
that.  It might be possible to implement, but it's outside the scope
of what svnsync does right now.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org