From owner-freebsd-stable Sun Sep 24 4: 7:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 0A4F937B422 for ; Sun, 24 Sep 2000 04:07:41 -0700 (PDT) Received: from parish ([62.253.88.205]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000924110738.LQF16640.mta01-svc.ntlworld.com@parish>; Sun, 24 Sep 2000 12:07:38 +0100 Received: (from mark@localhost) by parish (8.11.0/8.11.0) id e8OB7Yb00751; Sun, 24 Sep 2000 12:07:34 +0100 (BST) (envelope-from mark) Date: Sun, 24 Sep 2000 12:07:34 +0100 From: Mark Ovens To: Andre Goeree Cc: Brooks Davis , freebsd-stable@freebsd.org Subject: Re: FAQ's (was: Makeworld is dying...) Message-ID: <20000924120734.B252@parish> References: <39C42DF4.978A63C@urx.com> <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> <20000924104652.A1327@freebee.attica.home> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000924104652.A1327@freebee.attica.home>; from abgoeree@uwnet.nl on Sun, Sep 24, 2000 at 10:46:52AM +0000 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 24, 2000 at 10:46:52AM +0000, Andre Goeree wrote: > 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. > If you do forget to build a checkouts file first (as per Q12 of the cvsup FAQ) then there is a utility in the cvsup tarball (it doesn't get installed) which will list any dead files in your source tree. # cd /usr/ports/net/cvsupd-bin/ # make extract # cd work/cvsup-16.1/contrib/cvsupchk # ls README cvsupchk # cat README README.cvsupchk --------------- cvsupchk is a python script that checks a CVSup maintained directory hierarchy against the corresponding CVSup checkouts file. It looks for a number of anomalies: missing checked out files, deleted files being present, extra RCS files, 'dead' directories being present and so on. [snip] I just cp(1)'d it to /usr/local/bin. Although I followed Q12 when I first set up cvsup running cvsupchk after ~18 months it found loads of spurious files in /usr/src. Many of which were from when I'd been hacking and left old copies of originals and diff files etc. so it's useful for clearing these out. HTH > 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 -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message