Subject: Re: CVS Tree - sup wihout seperate copy of tree?
To: Curt Sampson <cjs@portal.ca>
From: Rick Byers <rickb@iaw.on.ca>
List: current-users
Date: 03/29/1997 18:25:08
On Sat, 29 Mar 1997, Curt Sampson wrote:

> > One more question though, is there any way to do the sup without having to
> > keep a copy of the tree?  It seems redundant to have the cvs files, the
> > working files, AND a sup directory.
> 
> There's no way around it, no.
> 
> > I was planning on having sup recieve the changed files into a temporary
> > directory, import them into my CVS tree, then delete the original supped
> > files.
> 
> The problem with that is that next time you sup, instead of just
> getting the set of changes, which will total perhaps a few megabytes,
> you'll have to pull down the entire source tree, which is over a
> hundred megabytes.

Hmmm... Are you sure?  I just modified sup to display "Would delete..." 
when it would normally delete a file that isn't in the repository, and I
supped into a new (empty) directory, and it only got the files that
changed from my last sup (4 meg in this case).  I was just going to import
those files, and then check the sup output for files that should be
removed.  Obviosly I'll eventually automate it all with a nice script
(thanks for giving me yours BTW - it was really helpfull).  I didn't use
the "keep"  option or the "old" option.  Isn't the point of the last.*
files so that it can only fetch the files which it hasn't supped before? 

Thanks,
	Rick

=========================================================================
Rick Byers                                      Internet Access Worldwide
rickb@iaw.on.ca                                      System Administrator
Welland, Ontario, Canada                                    (905)714-1400
http://www.iaw.on.ca/rickb/                         http://www.iaw.on.ca/