Date: Tue, 28 Nov 2006 13:47:30 -0500 From: Vivek Khera <vivek@khera.org> To: ports@freebsd.org Subject: Re: stale dependencies and portupgrade Message-ID: <2656DDD4-4241-4762-BA1B-D3CCEF9F573B@khera.org> In-Reply-To: <456C7DE1.5060204@FreeBSD.org> References: <5D017181-7215-4CB6-A459-4A40751AB39A@khera.org> <456C7DE1.5060204@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2656DDD4-4241-4762-BA1B-D3CCEF9F573B>