On 6/5/11 7:52 PM, Nico Kadel-Garcia wrote:
> On Sun, Jun 5, 2011 at 10:57 AM, Randolph, Christian [USA]
> <randolph_christian_at_bah.com> wrote:
>> 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.
>> Any suggestions would be greatly appreciated.
> If they can't communicate electronically, you'll have to synchronize
> by physical media. Subversion is built on top of CVS paradighms, with
> a central repository. Parall, disconnected development *cannot work*
> with that model, not without someone manually resolving all the
> inevitable discrepancies and merge issues in parallel code lines.
> This is a case where you need to lay out what your limitations on
> connectivity really are: no connections? No patches transmitted? No
> auto-propagation? Nothing? Then they're two independent projects, with
> entire source trees.
> If you need to be able to handle committed changes locally, in each
> repository, then you still have problems. Merging them is goin gto be
> difficult. You'll need to think in termos of a more distributed source
> control, such as git or possibly mercurial.
If it doesn't take too long for a round-trip, you could ship the working copy
from site B to site A, do the commit and update, and ship it back before doing
any more work at site B.
Received on 2011-06-06 04:19:36 CEST