Re: checking out modules into an existing directory

[Jason Allen]

I figured out a way to check the module out into an existing directory. I
simply created a CVS folder and then created an empty Entries file and
created a empty Repository file and add the name of the module to the
Repository file.

Now it works great, thanks for your help Matthew.

Jason A.
----- Original Message -----
From: "Matthew Riechers" <address@hidden>
To: "Jason Allen" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, July 11, 2001 6:54 AM
Subject: Re: checking out modules into an existing directory


> Jason Allen wrote:
> >
> > The directory I'm checking it out into, isn't controlled by CVS (no CVS
> > folders).
> >
> > I am using "cvs co -d dest module", I have also tried to just name the
> > module on the server the same as the existing directory and then check
it
> > out into one directory higher. I get the same problem.
>
> If you try to checkout into an existing directory, which would involve
> writing over that directory's contents (see below), CVS needs to know
> about that directory. Otherwise, you get the error described. This is a
> safety feature, kinda.
>
> Why don't you want to create a new directory?
>
> -Matt
>
> >
> > Thanks for your help,
> >
> > Jason A.
> >
> > ----- Original Message -----
> > From: "Matthew Riechers" <address@hidden>
> > To: "Jason Allen" <address@hidden>
> > Cc: <address@hidden>
> > Sent: Tuesday, July 10, 2001 2:47 PM
> > Subject: Re: checking out modules into an existing directory
> >
> > > Jason Allen wrote:
> > > >
> > > > Hi,
> > > >
> > > > I am having a problem checkout out modules into an
> > > > existing directory. If I try to do this I get the
> > > > following error:
> > > >
> > > > cvs checkout: in directory c:\temp\source:
> > > > cvs checkout: cannot open CVS/Entries for reading: No
> > > > such file or directory
> > > >
> > > > If I check the module out when there is no existing
> > > > directory and it creates a new one, everything works
> > > > fine. The problem is I need to be able to check it out
> > > > into an existing directory.
> > >
> > > Is that directory already controlled by CVS?
> > >
> > > >
> > > > Anyone know a way to fix this?
> > > >
> > > > Thanks,
> > > >
> > > > Jason A.
> > >
> > > What command did you run?
> > >
> > > Are you trying to do 'cvs co -d source module'? That doesn't mean
> > > 'create directory source\module'. It means 'create a sandbox dir
called
> > > "source" for module'.
> > >
> > > It won't work if CVS doesn't know about that directory. 'cvs co' on an
> > > existing sandbox effectively does a 'cvs update'
> > >
> > > HTH,
> > >
> > > -Matt
> > >
> > > _______________________________________________
> > > Info-cvs mailing list
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/info-cvs
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/info-cvs
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com