[lug] CVS? Syncing repositories?

[Scott A. Herod]

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