Subject: Re: Upgrading from 1.5.2 to -current?
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: Greg A. Woods <woods@weird.com>
List: port-sparc
Date: 04/22/2002 15:36:24
[ On Monday, April 22, 2002 at 21:13:08 (+0200), Manuel Bouyer wrote: ]
> Subject: Re: Upgrading from 1.5.2 to -current?
>
> On Mon, Apr 22, 2002 at 03:08:29PM -0400, Greg A. Woods wrote:
> > [ On Monday, April 22, 2002 at 19:24:32 (+0200), Manuel Bouyer wrote: ]
> > > Subject: Re: Upgrading from 1.5.2 to -current?
> > >
> > > Yes, but this doesn't work if there are different modules depending on
> > > the tag (i.e. it won't get modules that are in the branch but not on truck,
> > > or vice-versa). This is the problem.
> > 
> > huh?  i'm not aware of any tag-dependent modules in the NetBSD CVS
> > repostitory, certainly not anything recent.  The last significant change
> > to the modules organisation was 1999/05/25, and so far as I can see that
> > still wouldn't affect anything related to the "src" alias module in any
> > currently available tar "official" files for -current or 1.5.2....
> 
> For example, a directory has been moved, which is not in the base
> module (it's in syssrc if I remember properly), so without an existing
> entry in CVS/Entries cvs update won't create it.

are you talking/thinking about:  src/usr.sbin/dbsym  ?
(which is part of the _syssrc-cmp "sub-"alias module)?

Yes, you're right that this directory will not be created by "cvs update
-A" under certain circumstances.  It has been removed on -current.  That
means you can't convert a -current working directory checked out using
the "src" (or "syssrc", or "src-nocrypto", or "src-crypto-us", or
"src-crypto-all", or any of the internal-only aliases) to a
release-branch working directory without manually mucking about to check
it out in the correct location.

I should have mentioned that "cvs update -A" is really something only
CVS experts should use and only with great care, but I didn't want to
confuse the issues given that it's in the documented procedure and I
really don't know without looking what the state of the CVS
administrative files is in the distributed source tars.....

When in doubt always start with a fresh checkout....   :-)

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>