Re: binutils+gdb CVS module

[Daniel Jacobowitz <drow@mvista.com>]

On Mon, Aug 18, 2003 at 05:51:26PM +0300, Stephen Biggs wrote:
> On Mon, 2003-08-18 at 15:56, Daniel Jacobowitz wrote:
> > On Mon, Aug 18, 2003 at 05:04:44AM -0400, Michael Elizabeth Chastain wrote:
> > > The normal workaround is to do "cvs update" almost all of the time, with
> > > no "-d", and to handle new top-level files and directories specially.
> > > Fortunately they don't appear very often (a few times a year).
> > 
> > The trick is to update directories the same way you checked them out
> > initially: say "cvs -d <root> co gdb+binutils" from the level above
> > src, just like the first time.  That gets the right set of new files.
> > 
> 
> I did a checkout like so:
> $ cd ~/cvs
> $ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src login
> $ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src checkout
> binutils+gdb
> 
> ... so, if I have ~/cvs/src being the top of my binutils+gdb tree (with
> NO mention anywhere of binutils+gdb in the tree, fitting what Michael
> said), from the level above, if I understand you correctly?
> 
> This doesn't work.
> $ cd ~/cvs
> $ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src update -R -d -P
> binutils+gdb
> cvs server: Updating binutils+gdb
> cvs server: cannot open directory /cvs/src/binutils+gdb: No such file or
> directory
> cvs server: skipping directory binutils+gdb
> $
> 
> What did I do wrong?

Try using "checkout" the second time too.  That's the key - update
doesn't check the modules file, only checkout does.  Don't need to give
it any other options than you did the first time.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer