[Top][All Lists]

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

Re: moving repo

From: Eric Siegerman
Subject: Re: moving repo
Date: Thu, 1 Mar 2001 21:57:34 -0500
User-agent: Mutt/1.2.5i

On Thu, Mar 01, 2001 at 08:40:01AM +0000, Martin Tomes wrote:
> >>>>> "Rob" == Rob Helmer <address@hidden> writes:
>     Rob> [...] I am wondering about people's experiences moving repositories
> I have a perl program which you can modify and use to switch peoples checked
> out code to use the new repository.  We have moves ours several times without
> problems.  If you want the program mail me.

To avoid having to deal with this again next time, do the
  - wherever you physically put the repo on the new machine, make
    a symlink to it in a standard location (my own convention is
  - make a DNS alias (ie. CNAME) for the CVS server machine (my
    convention is "cvs") -- you can also do this in /etc/hosts,
    of course, if that's how you run your network

Tell people to check out their new sandbox using:
        cvs -d co ...
instead of using either the machine's real name or the repo's
real pathname.

Then, if you ever have to move the repo to a new server, or to a
new (eg. larger) partition on the same server, you can do it
transparently by changing the appropriate pointer(s).

Of course you can invent your own conventions if mine aren't to
your taste ...  but once you do, stick to them!


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)

reply via email to

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