[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Two-Site Subversion Repository Setup Ideas

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Mon, 06 Jun 2011 07:52:41 -0500

On 6/6/11 7:33 AM, Heinrichs, Dirk wrote:
> Am Montag, den 06.06.2011, 11:55 +0200 schrieb Andreas Tscharner:
>>> I am looking for suggestions from the community as to how
>>> best address the setup issue outlined below.
>>> We have two sites wanting to use Subversion that are
>>> performing parallel development of the same software. Due to
>>> security restrictions, the two sites are unable to
>>> communicate electronically; all data transfers must be via
>>> media (CD-ROM/DVD). Site A is the main site and is
>>> responsible for overall configuration control.
>>> Is there a way to setup the two subversion repositories to
>>> somehow automate keeping the two repositories in sync? We
>>> are usually passing media back and forth once a week, but
>>> currently we are doing a manual sync process that is both
>>> time-consuming and error-prone.
>> People here will hate me for this, but I think you should switch to a
>> DVCS (Distributed Version Control System), like Mercurial or git. While
>> I don't know git, in Mercurial you have the possibility to save and
>> export you changes as so-called bundle at one site and import them at
>> the other site. For more information:
>> http://www.selenic.com/mercurial/hg.1.html#bundle
> Monotone has similar capabilities, too. And there's ClearCase(tm) with
> MultiSite(tm), of course (if your management is willing to spend some
> $$$).

If you are doing this in 2 directions, won't the disconnected repositories
eventually drift out of sync as the people resolving conflicts make different
choices - regardless of how well the VCS manages the details?

   Les Mikesell
Received on 2011-06-06 14:53:18 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.