From owner-freebsd-questions@FreeBSD.ORG Wed Jun 23 06:56:55 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEBF916A4CE for ; Wed, 23 Jun 2004 06:56:55 +0000 (GMT) Received: from fed1rmmtao10.cox.net (fed1rmmtao10.cox.net [68.230.241.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB9743D5F for ; Wed, 23 Jun 2004 06:56:55 +0000 (GMT) (envelope-from mnavarre@cox.net) Received: from reichlieu.lan ([68.6.195.68]) by fed1rmmtao10.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040623065636.IRKP5491.fed1rmmtao10.cox.net@reichlieu.lan>; Wed, 23 Jun 2004 02:56:36 -0400 Received: from reichlieu.lan (localhost [127.0.0.1]) by reichlieu.lan (8.12.11/8.12.11) with ESMTP id i5N6ubFO087410; Tue, 22 Jun 2004 23:56:37 -0700 (PDT) (envelope-from mnavarre@reichlieu.lan) Received: from localhost (localhost [[UNIX: localhost]]) by reichlieu.lan (8.12.11/8.12.11/Submit) id i5N6ubw1087409; Tue, 22 Jun 2004 23:56:37 -0700 (PDT) (envelope-from mnavarre) From: Matt Navarre To: Kent Stewart Date: Tue, 22 Jun 2004 23:56:37 -0700 User-Agent: KMail/1.6.2 References: <20040622220538.34e5e5a5@localhost> <200406222219.47739.mnavarre@cox.net> <200406222334.01861.kstewart@owt.com> In-Reply-To: <200406222334.01861.kstewart@owt.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406222356.37063.mnavarre@cox.net> X-SA-Scanned: 0 () X-Scanned-By: MIMEDefang 2.41 cc: freebsd-questions@freebsd.org Subject: Re: cvsup and ports INDEX X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 06:56:56 -0000 On Tuesday 22 June 2004 11:34, you wrote: > > > > That's not what the man page implys: > > > > > > "The portsdb command is a tool to generates the ports database > > named INDEX.db from the ports index file named INDEX. It is commonly > > used among the tool suite and automatically updated on demand when it > > gets older than the index file" > > > > I'm not sayin' you're wrong, since I read that a long while ago and > > haven't needed to know anything more about portsdb since, but you and > > the description in portsdb(1) seem to disagree. > > > > Yes, the -U option does "Update or create the ports index file called > > INDEX", it's just not evident from the description that it can use > > the installed ports tree. > > If you are to run it after you cvsup ports-all, what do you think it is > using? The INDEX file that get cvsup'ed when I cvsup ports? I only sup ports once a month or so unless I'm installing something new, so I guess I'm getting a new INDEX most times. > > In addition, portsdb -U now runs "make index" but you would have to > search -ports@ to read about that change. You can read comments about > it on > http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/portupgrade/Makefile > see the commit message for version 1.78. Well, I don't track -ports, so, yes I missed that. I'm not trying to be combative here, I was wrong, a bit. I gave the portsdb man page a quick once-over a while ago (when I started using portupgrade) and thought I understood what it was doing. I didn't realize the -U was regen'ing INDEX from the current ports tree, as I didn't realize that INDEX was updated with less frequency that the tree, so I didn't realize that was even needed, though it's obvious once I think about it. It also explains why portsdb -Uu takes so freekin' long sometimes, which had been bugging me. > > Kent > > > So I was kinda right. A little :) > > > > > Kent > > > > Matt -- "We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there." -- Dana Gould