[lug] CVS? Syncing repositories?

Riggs, Rob RRiggs at doubleclick.net
Tue Feb 19 09:40:06 MST 2002


"the consensus is to have everything live in one place."

This may have some merit that I am not aware of. You either have a single,
company-wide repository, or you live with seperate repositories, knowing
that some project components exist in other repositories. The open-source
model is a great example of the latter. I don't think it would be wise to
copy code into other repositories, risking a fork in development or a real
CM nightmare later on.

A more pragmatic approach might be to start packaging you utility libraries
as discreet products. That way these individual components just need to be
installed as pre-compiled objects on the development systems (and the test
and production systems if they are shared libraries). Just think of it as a
dependency, such as with any other optional system library, rather than
making it a tightly coupled component of the system.

Would such a scheme work in your development environment?

-Rob


-----Original Message-----
From: Scott A. Herod [mailto:herod at interact-tv.com]
Sent: Saturday, February 16, 2002 1:31 PM
To: lug at lug.boulder.co.us
Subject: Re: [lug] CVS? Syncing repositories?


I've got a set of utility libraries that exist on one cvs server.
They are now going to be used on a project that resides on another
server, and the consensus is to have everything live in one place.

As I consider it, I suspect that the existing source will have to
branch for the new project.  Perhaps it's best to set a tag, import
the existing code into the new repository, have everyone work from
the new repository, and merge changes back into the initial repository
as necessary.

Thanks for the responses,

Scott Herod


Tom Tromey wrote:
> 
> >>>>> "Scott" == Scott A Herod <herod at interact-tv.com> writes:
> 
> Scott> Does CVS support a method to sync two repositories?  I suppose
> Scott> it would be reasonably easy to update from one and commit to
> Scott> the other but that seems too prone to merge errors to be easily
> Scott> automated.
> 
> What is your goal?
> 
> You can sync repositories using rsync or CVSup.  But with both of
> these there is a single master repository, and the others are
> basically read-only mirrors.  (This is useful for providing anonymous
> cvs access.)
> 
> Automatically synchronizing two repositories, both of which are
> read-write, is hard or impossible, depending on what you expect out of
> it.  In the end (in the general case) it always requires a human to
> resolve conflicts.
> 
> Tom
_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug



More information about the LUG mailing list