Hello Mathew,

  re intermediate build files, I don't quite see why you'd have
to lose them. Just copy them over.

  To clarify, what I meant by step B is a raw copy of every file
in your old working dir to the new working dir. AFAICT the only
thing you have to worry about are files that you got rid of in the
old working directory and which show up in the new working
directory. Probably those files were deleted and 'cvs remove'd
but not yet committed. So that information will be lost, but
that's just a matter of 'cvs remove'ing them again.

  The basic idea of a new checkout and a raw copy is actually
a renewal of the CVS/Root files without bypassing cvs.

  That said, I agree that the other solution sounds better. Haven't
had the chance to test it though I guess you've taken care of that.

Erik





"Riechers, Matthew W" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/05/2002 03:25 PM

 
        To:     [EMAIL PROTECTED]
        cc:     Mike Ayers <[EMAIL PROTECTED]>, CVS <[EMAIL PROTECTED]>, i 
Xicheng 
Jia <[EMAIL PROTECTED]>
        Subject:        Re: Newbie Problem: About repositiory


[EMAIL PROTECTED] wrote:
> 
>   A. checkout new working dir using new repository location
>   B. transfer content of old working copy to new working copy
>   C. delete and cvs remove files from new working copy if necessary
>   D. get rid of old working copy and continue work in new working copy

That is pretty fool-proof, but you lose existing intermediate build
files, which may or may not be a big deal.

> Mike Ayers <[EMAIL PROTECTED]>
>
>                  4.  Run a script which deletes all the CVS/Root
> directories and then
> `cvs -d /new/path/to/repository update`

s/directories/files/ and this works. Nice tip! Much better than running
N processes to delete/modify existing files...

Also note that if $CVSROOT is defined to the new location, you can just
'cvs up'. 

-Matt


_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs





_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to