[Top][All Lists]

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

Re: Using cvsup mirror for a fast checkout

From: Todd Denniston
Subject: Re: Using cvsup mirror for a fast checkout
Date: Fri, 22 Nov 2002 10:49:27 -0500

Chris Sharpe wrote:
> I've got several remote sites that have slow links and large
> checkouts are too slow (for their satisfaction).
> Here's my plan:
> 1) Use cvsup to create a read-only mirror that is local to them.
> Update this at least once a day.  Prevent checkins here.
> 2) Create a wrapper around 'cvs checkout' which will take their
> $CVSROOT from the environment or from a -d argument, change
> the hostname from the master server to their local mirror,
> and then pass that along as the new -d arg to 'cvs checkout'.
> So ":method:address@hidden:/archive" becomes
> "method:address@hidden:/archive".
> After getting a checkout from the cvsup local mirror, it then
> traverses the tree and changes all of the CVS/Root files
> back to using the master server.
> 3) Now all future cvs operations (update, log, commit, etc.)
> will operate directly with the master, but the amount of data
> going back and forth over the net is far lower.
> Any holes in this?
> It seems that since cvsup is creating an exact duplicate from the
> master, all of the CVS/Entries data should be in sync as well.
> And the first update will pull over changes made since the mirror
> was last updated.
If you are going to do step 2 so 3 happens why not just make a tar.bz2 at your
local site and copy that to the remote site on the period that you would have
done the cvsup, and wrapper cvs checkout to untar the file and change
":method:address@hidden:/archive" to
":method:address@hidden:/archive" then do a cvs -z9 update 

Assuming a cvsup period of at least longer than once every 2 or 3 days?

if they were still doing updates, logs and diffs against a cvsup server, then
making the change to the master at commit time (which they would be reminded to
do as you are not allowing writes to the files in the cvsup server),  I would
see cvsup as the better solution.

Todd Denniston, Code 6067, NSWC Crane mailto:address@hidden
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power

reply via email to

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