From owner-freebsd-ports Fri Apr 14 6:59:36 2000 Delivered-To: freebsd-ports@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 29E2737B754 for ; Fri, 14 Apr 2000 06:59:30 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id GAA99245; Fri, 14 Apr 2000 06:59:28 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id GAA24943; Fri, 14 Apr 2000 06:59:28 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14583.9279.731684.583301@whale.home-net> Date: Fri, 14 Apr 2000 06:59:27 -0700 (MST) To: Will Andrews Cc: ports@FreeBSD.ORG Subject: Re: make index broken? In-Reply-To: <20000414065027.B19141@argon.blackdawn.com> References: <14582.44973.654107.980182@whale.home-net> <20000414065027.B19141@argon.blackdawn.com> X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Friday, April 14, Will Andrews wrote: ] > > Why are you using ``make index'' anyway? The only thing it does is generate > INDEX, which isn't awesomely useful for the average person since Satoshi > regens it himself every now and then. Overwriting ports/INDEX brings a risk > - cvs (or whatever tool you use) may think the previous revision (which is > supposed to be on your system) is broken/gone/fubar'd/whatever. The INDEX > file is pretty darn big.. ;) Well, the CVS thing is not a terrible concern to me. The reason I'm using it is because the INDEX file is not updated but only "every now and then." When I CVSup the ports, I like using pkg_version to tell me what has been updated. This works using the INDEX file. If a port was updated but the INDEX file didn't show that it was updated to a new version, pkg_version would not be able to tell me .... > > > I do suppose perhaps you simply ignore cvs/cvsup on ports/INDEX and regen > it yourself every few days or something. That could save download time, but > certainly not CPU or I/O time. :) aaaa .... got plenty of CPU and I/O to go around ;-) > It is my suspicion that this is caused by PORTNAME/PORTVERSION. this was happening before that switch over last weekend--I just didn't have the time to write to -ports about it. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message