Veronica,
I have experienced similar mysterious happenings... and tracked it
down to this: It appears to me that :
CVS stores the location of the repository used in a "get" or "update"
operation in the CVS/Root file of the working directories.
When you then do subsequent cvs operations, it uses the contents
of this file in preference to the CVSROOT envrionment variable or
what is specified in the dialogs of WinCVS (when using that front end).
The solution I am using, is to delete all the "Root" files via a
simple Unix find command and then set the CVS_IGNORE_REMOTE_ROOT
enviromnent variable for the shell of all subsequent cvs operations...
This prevents cvs from writing out a new value into the Root file
again... and the absence of the Root file, forces CVS to use your
envronment variable or settings you have set.
(the equivalent to setting CVS_IGNORE_REMOTE_ROOT for the WinCVS client
seems to be by setting the registry entry of
HKEY_CURRENT_USER\Software\WinCVS\wincvs\CVS settings\P_AlwaysUseCvsroot
to the value 1 ; I figured this out by messing with it myself, so I
won't guarantee it is the right answer and will always work... but it
does for me !)
Don't ask me why CVS thinks the contents of that file is so important
when all the documentation points to the -d switch or environment
variable being the truth.
If this is the completely wrong answer to your problem, I feel happy
to at least have shared some of my experiences with you all...
cheers
jb.
On Wed, May 31, 2000 at 05:40:37AM -0700, Veronica Lee wrote:
> Then how does CVS know which box's repository I am trying to access?
>
> I have CVS istalled on box A and B.
> I would telnet into Box B.
> Login to CVS Server on Box A: /usr/local/bin/cvs -d
> :pserver:veronica@boxA:/usr/local/repos_on_A login
>
> To this point it has been successful.
>
> However, if I try to check out a module, I ran into problems.
>
> /usr/local/bin/cvs -d co /usr/local/repos_on_A/myproj (failed)
> /usr/local/bin/cvs -d co repos_on_A/myproj (failed)
>
> It appears that instead of looking for /usr/local/repos_on_A/myproj on
> Box A, it looked for the repository on box B. When it cannot find it,
> CVS gave me errors.
>
>
>
> --- Larry Jones <[EMAIL PROTECTED]> wrote:
> > Veronica Lee writes:
> > >
> > > Do we need to install CVS Server on box B as well to use it as a
> > > client?
> > > Or is there any other tool we need as a CVS client in UNIX.
> >
> > You need *some* kind of CVS client -- the way it's typically built,
> > the
> > Unix version of CVS is a client, a server, and a stand-alone CVS all
> > in
> > one, so you can use it as a client without installing it as a server.
> >
> > There are also a number of GUI clients you can use -- see
> > www.cvshome.org for details.
> >
> > -Larry Jones
> >
> > Isn't it sad how some people's grip on their lives is so precarious
> > that they'll embrace any preposterous delusion rather than face an
> > occasional bleak truth? -- Calvin
>
>
> =====
> ====================================================
> veronica lee [EMAIL PROTECTED]
> ====================================================
> "Kindness comes from a place in the heart." ~Flavia
>
> __________________________________________________
> Do You Yahoo!?
> Send instant messages & get email alerts with Yahoo! Messenger.
> http://im.yahoo.com/
>
