Re: Help with moving repository

[Mark Cooper]

Laurence Jones wrote:
>Also, to prevent this problem from reoccurring
>in the future, you should set up a virtual host name for your CVS server
>(something like "cvs")

Yep, we've done that :) (We saw it coming).

Anyway, I've written a couple of small .bat files which do the trick for
WinDoze client users.

All you have to do is set the CVSROOT environment variable to what it
should be then run the first batch file (changecvs.bat), from the root of
the drive or directory where you have CVS working copies.

changecvs.bat:
for /R %%f in (CVS\Root) do call changeroot.bat %%f

changeroot.bat:
if not exist %1 goto end
copy %1 %1.old
echo %CVSROOT% >%1
:end

I tested it on my working copies and it worked a treat.

Thanks to those who responded.

Mark Cooper





address@hidden (Larry Jones)@thor.sdrc.com on 20/01/2003 15:56:54

Sent by:    address@hidden


To:    address@hidden (Mark Cooper)
cc:    address@hidden

Subject:    Re: Help with moving repository


Mark Cooper writes:
>
> Is there a utility available anywhere to perform global changes to the
cvs
> metadata in a users working copy. For instance change the entry in
cvs/root
> from ":pserver:address@hidden:/cvs/cvsroot" to
> ":pserver:address@hidden:/cvs/cvsroot". I can imagine that someone somewhere
> has done this before.

Such utilities have been posted to the list before -- I suggest
searching the archives.  Also, to prevent this problem from reoccurring
in the future, you should set up a virtual host name for your CVS server
(something like "cvs") and make it an alias for the actual machine name.
If you have to move the repository again in the future, all you have to
do is change the definition of the alias to point to the new machine,
the users don't have to do anything at all.

-Larry Jones

 I don't see why some people even HAVE cars. -- Calvin