We did this recently and had to write a script for
people to update their local views. We are also
developers using NT, so we avoid this problem from happening
in the future by all setting our CVSROOT variables to
a drive letter instead of to the actual host. For
example, if our source control is in the directory
\\engsrv\development\source
I'll make "development" a network share and then mount it from
my developer machine as drive S. Then I set CVSROOT to
:local:s:\source
Next time the source repository moves, I won't need to run any
update scripts.
take care,
Jon
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 26, 2000 12:20 AM
> To: CVSINFO
> Subject: Moving repository: best way to handle this?
>
>
> I have to move our repository from a mchine to another and in
> the same time
> I'll switch to server mode. This is on NT so symbolic links
> tricks won't
> help...
>
> What's the best and easiest way to do this given that a numer
> of users are
> working on projects and have files checked out?
>
> Should I:
> 1) write a script which fixes all the refs to the old
> repository in the
> Repository files (plus fix their CVSROOT)?
>
> or
> 2) have them either commit or forget about their current
> changes, remove
> their working copy and checkout from the new repository?
>
> Can anyone share experience in doing that?
>
> Thanks,
>
> D.
> ------------------------------------
> Dominique de Waleffe
> Mission Critical
> Tel: + 32 2 757 10 15
> Email: [EMAIL PROTECTED]
>
