[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bidirectional repository synchronization with CVSup - how?

From: Greg A. Woods
Subject: Re: Bidirectional repository synchronization with CVSup - how?
Date: Fri, 21 Sep 2001 21:45:23 -0400 (EDT)

[ On Friday, September 21, 2001 at 15:40:23 (-0500), Art Eschenlauer wrote: ]
> Subject: Bidirectional repository synchronization with CVSup - how?
> We develop software using CVS as an SCM tool. Our developers are
> located at multiple sites linked by a moderate-speed,
> moderate-reliability network. CVSup seems like the tool to use to
> replicate.

Probably not, actually....

The only way CVSup will work for you is if you can:  (a) choose one
actual site as the real master site and replicate out from there; (b) do
all work at slave sites on branches; and (c) dedicate someone to doing
merges from the site branches to some master branch.

CVSup cannot work miracles.  It is only able to share changes between a
master site and one or more slave sites if the changes at slave sites
occur on branches which are guaranteed to be absolutely unique to the
given site.

If you go look at the research into distributed databases you'll find
that you're asking to solve a problem that the research community still
doesn't consider to be solved to the extent necessary for real-world
production uses.

>  - bitkeeper is not (yet) an option for us

That's too bad because BK solves this problem in a very elegant and
effective fashion (by avoiding it all together and instead treating all
change sets as independent lines of development and allowing anyone and
everyone to have a full "master" copy of a shared repo).

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]