[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]
Re: Good utility for CVS
Sorry for late replies. Perforce too does not have a distributed server
architecture. That means two repositories with continuous activity cannot
be synced without the export-import you mentioned (which stops activity on
at least one server). This limits the development process only to people
with fast network access to the CVS server.
I checked again at cvshome.org and found some info to do this at:
This sounds complicated but at least it's possible for CVS.
Thanks to all,
On Mon, 5 Mar 2001, Arun Sharma wrote:
> On Mon, Mar 05, 2001 at 06:56:35PM +0530, Binand Raj S. wrote:
> > Indraneel Majumdar forced the electrons to say:
> > > I'm in search of an automated CVS syncing tool (eg if I have the same CVS
> > > repository at two places and want them synced every 2 hours)
> > That would be rsync over ssh, run every two hours from cron. You might want to
> > block port 2401 at both locations while the sync is going on, if the repository
> > is large.
> That'd work only if both the cvs repositories are read only. If people are
> checking in stuff to both CVS repositories and you have to sync them, there
> is nothing short of a checkout -> tar -> transfer -> import to vendor branch.
> http://www.perforce.com/ might be interesting. Free for writing open source