From owner-freebsd-ports@FreeBSD.ORG Thu Jul 19 00:55:29 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B22A16A401 for ; Thu, 19 Jul 2007 00:55:29 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id D738013C478 for ; Thu, 19 Jul 2007 00:55:28 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by turtle-in.mxes.net (Postfix) with ESMTP id DD96910573 for ; Wed, 18 Jul 2007 20:22:24 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 3A7B05193C for ; Wed, 18 Jul 2007 20:22:22 -0400 (EDT) Date: Thu, 19 Jul 2007 01:22:18 +0100 From: RW To: freebsd-ports@freebsd.org Message-ID: <20070719012218.34cd2c43@gumby.homeunix.com.> In-Reply-To: <20070718154452.B3091@math.missouri.edu> References: <20070718154452.B3091@math.missouri.edu> X-Mailer: Claws Mail 2.9.2 (GTK+ 2.10.13; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Problems with +CONTENTS being messed up by pkg_delete -f X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2007 00:55:29 -0000 On Wed, 18 Jul 2007 15:56:49 -0500 (CDT) Stephen Montgomery-Smith wrote: > > If you "pkg_delete -f" a package and then install the port again (but > after it has been bumped up a version), then the +CONTENTS of ports > that require the original port will be incorrect. This apparently > messes up programs like portmanager In what way does that mess-up portmanager? portmanager relies on these inconsistencies to determine which ports should be rebuilt. You have to be careful about how you mix portmanager and portupgrade usage for this very reason. If you have the ports system itself faking dependency self-consistency then you might as well remove portmanager from the ports tree.