From owner-freebsd-ports@FreeBSD.ORG Wed May 4 21:14:52 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6C5A16A4CE for ; Wed, 4 May 2005 21:14:52 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C7FD43D58 for ; Wed, 4 May 2005 21:14:52 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from localhost (24-53-250-148.pittpa.adelphia.net [24.53.250.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id A550F69A21; Wed, 4 May 2005 17:14:00 -0400 (EDT) Date: Wed, 4 May 2005 17:13:59 -0400 From: Bill Moran To: Jim Campbell Message-Id: <20050504171359.6583950f.wmoran@potentialtech.com> In-Reply-To: <4279312F.20207@charter.net> References: <4279312F.20207@charter.net> Organization: Potential Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: wxs@csh.rit.edu cc: freebsd-ports@freebsd.org Subject: Re: Problem with portsdb X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 21:14:52 -0000 [Please keep the mailing list in the loop, primarily so this information gets archived so the the next person searching can find it.] Jim Campbell wrote: > Wesley and Bill, > > You both suggested the same solution. Before I go off and do it, I need > to be clear about something. Having done a "make fetchindex" I should > NOT do a "make index" or "portsdb -uU" since that would overwrite the > just-fetched INDEX. Is this correct? That's correct. If you run "make index" it will overwrite what you just fetched, thus undoing the fetchindex. portsdb with -U will do the same as a "make index". It's OK to do a "portsdb -u", but this isn't required, as it will do this on demand anyway. If you've got an up-to-date version of portupgrade, it actually does the fetchindex for you when it notices things are out of date, but older versions automatically do "make index" ... so make sure your portupgrade is updated first. -- Bill Moran Potential Technologies http://www.potentialtech.com