Date: Sun, 24 Sep 2000 10:46:52 +0000 From: "Andre Goeree" <abgoeree@uwnet.nl> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-stable@freebsd.org Subject: Re: FAQ's (was: Makeworld is dying...) Message-ID: <20000924104652.A1327@freebee.attica.home> In-Reply-To: <20000924003413.A2018@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Sun, Sep 24, 2000 at 12:34:13AM -0700 References: <39C42DF4.978A63C@urx.com> <Pine.LNX.4.10.10009170918240.13465-100000@shark.harmonic.co.il> <20000917160006.D67912@wantadilla.lemis.com> <20000918154418.P8111@moose.bri.hp.com> <20000924095410.A65590@wantadilla.lemis.com> <20000924092354.A473@freebee.attica.home> <20000924003413.A2018@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 24, 2000 at 12:34:13AM -0700, Brooks Davis wrote: > On Sun, Sep 24, 2000 at 09:23:54AM +0000, Andre Goeree wrote: > > I think a lot of people start cvsuppin' without checking out > > their source tree against the known version of code they have. > > ie. if you have 4.0-R, cvsup with tag RELENG_4_0_0_RELEASE once > > and then track RELENG_4. > > > > Omitting this step could lead to (if you cvsup from 4.0-R for example) > > a lot of inconsistencies, stale files that should have been > > deleted, etc in the source tree which could cause problems > > in (future) buildworlds. Ok, i'm not an expert but that's my > > personal experience.. > > > > Unfortunately a lot of people (including me) only start reading > > the FAQ's when they get in trouble.. so a hint (ie. read this first..) > > in the right place could prevent this kind of trouble. > > > > Then again, i could be totally wrong about this, i'm no expert. > > This is just plain wrong. If you can actually duplicate this problem > I'm sure John Polstra (jdp@FreeBSD.org) would love to hear about it, > but that's certaintly not the way CVSup or CVS is supposed to work. > There's really nothing special about RELENG_4_0_0_RELEASE vs RELENG_4 > since RELENG_4_0_0_RELEASE is just a snapshot in time on the RELENG_4 > branch. > > -- Brooks Hello Brooks, The tag itself in fact has nothing to do with it. It's the point that cvsup will not delete any files without a checkouts file and that this IMHO could lead to inconsistencies in the source tree or at least a lot of stale files dangling around. By taking the steps mentioned in Q-12,13 of the cvsup-faq you can prevent this. This is also where the tag RELENG_4_0_0_RELEASE comes in and it's only purpose is to create a checkouts file for later use. The handbook doesn't mention that it could be a good idea to follow these steps (cvsup-faq Q12,13). That's the only point i'm trying to make clear. I'm certainly not saying there's something wrong with CVSup / CVS or how they work, i think it's very reliable software. FYI: After the first time i cvsupped from 4.0-R (cdrom) to 4.1-S without taking the steps mentioned above, my buildworld died at some place. Nobody else had this problem (it was not discussed in the list). So, it should be something in the local source tree. After that i started again from the cdrom sources but this time i followed the steps in cvsup-faq Q12,13 when i cvsupped the first time. Never had any problems since :) Hey, i said that i could be wrong ;) Regards, -- Ago To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000924104652.A1327>