From owner-freebsd-ports@FreeBSD.ORG Tue Nov 28 18:47:36 2006 Return-Path: X-Original-To: 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 7AA8D16A49E for ; Tue, 28 Nov 2006 18:47:36 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [74.92.149.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1F1543CAE for ; Tue, 28 Nov 2006 18:47:28 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id E9A83B814 for ; Tue, 28 Nov 2006 13:47:31 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <456C7DE1.5060204@FreeBSD.org> References: <5D017181-7215-4CB6-A459-4A40751AB39A@khera.org> <456C7DE1.5060204@FreeBSD.org> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-13--398626264; protocol="application/pkcs7-signature" Message-Id: <2656DDD4-4241-4762-BA1B-D3CCEF9F573B@khera.org> From: Vivek Khera Date: Tue, 28 Nov 2006 13:47:30 -0500 To: ports@freebsd.org X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: stale dependencies and portupgrade 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: Tue, 28 Nov 2006 18:47:36 -0000 --Apple-Mail-13--398626264 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Nov 28, 2006, at 1:20 PM, Doug Barton wrote: >> I suppose the bug is that I expected portupgrade -Rr to recompute >> the dependency lists of the upstream ports to take into account >> any changing dependencies of the updated port. >> Do other port manager utilities take this type of change into >> account? At this point, I'm not sure any of my dependencies are >> accurate on the complex ports like RT. > > This type of complexity is one of the reasons why portmaster does > not use an "extra" database to track dependencies. It instead > relies on /var/db/pkg and the ports framework to do that, and > updates the +CONTENTS files themselves when needed. > I think the ports infrastructure also needs to be able to specify which dependencies are directly linked to a given port and which ones are inherited. Else the only way to do it is to recompute the full list from the "top of the tree" for ports like RT. I'll have a look at portmaster. Do I have to chase up the tree to find the top level port or can I just "portmaster p5-Expect" and have it chase all the way up and fix everything that depends on that port? --Apple-Mail-13--398626264--