[Top][All Lists]

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

RE: multiple repositories or multiple work locations

From: Arthur Barrett
Subject: RE: multiple repositories or multiple work locations
Date: Thu, 11 Sep 2008 06:50:44 +1000


> can some one help me on how to maintain multiple repositories 
> of the same
> code base at two different geographical locations.

I just answered this yesterday in the thread 'RE: List of directories
under a "top-level" module'...

Why do you want to do this?

This question is usually asked by people who are not using CVS well and
therefore experiencing performance issues.  CVS was designed over 20
years ago for use on networks that ran at a fraction of the speed of
todays slowest networks - you never ever ever need more than one
repository server to solve performance issues even on the slowest

See my many previous posts about this issue:
And many many more...

(Note your e-mail reader may 'split' those links over multiple lines, so
you may need to paste them together before using them).

If for some reason you cannot fix your processes to use CVS well, then
one options is to use CVSNT 2.5.04 for repository replication (yes it is
GPL and runs on linux, in fact our CVSNT repository runs on debian).
Our main two development centres are in Sydney Australia and Manchester
UK and we use a "write through, sync back" repository for this purpose
(well actually the "purpose" is/was to prove it works, not to actually
solve any problem).

If you want more info on the repository replication stuff please see the
previous newsgroup posts:

Note: if you are interested in CVSNT there is a separate newsgroup,
website etc for it - do not post CVSNT specific questions to the CVS

Note2: CVS and CVSNT are very different products - in my experience
people who I've met who use CVS love it for its simplicity and elegance.
People who use CVSNT on the otherhand love it for its breadth of inbuilt
features (things like mergepoints, changesets/atomicity, user defined
changesets, failsafe audit, access contol lists, support for reserved
and unreserved versioning) which is rather the opposite of 'simplicity'.


Arthur Barrett

reply via email to

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