From owner-freebsd-ports@FreeBSD.ORG Sat Aug 21 22:03:08 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3737106566C for ; Sat, 21 Aug 2010 22:03:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 7E6598FC17 for ; Sat, 21 Aug 2010 22:03:08 +0000 (UTC) Received: (qmail 32559 invoked by uid 399); 21 Aug 2010 22:03:07 -0000 Received: from localhost (HELO laptop.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Aug 2010 22:03:07 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Date: Sat, 21 Aug 2010 15:03:06 -0700 (PDT) From: Doug Barton To: Rob Farmer In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: Outlook -- Not just for spreading viruses anymore! OpenPGP: id=1A1ABC84 Organization: http://SupersetSolutions.com/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-ports Subject: Re: portmaster and build depends 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: Sat, 21 Aug 2010 22:03:08 -0000 On Sat, 21 Aug 2010, Rob Farmer wrote: > I just came across what I think is a potential problem in portmaster > (3.0). I csup-ed today and ran portmaster -a. This machine had ports > last updated on August 9th. > > ===>>> The following actions will be taken if you choose to proceed: > Upgrade en-freebsd-doc-20100625 to en-freebsd-doc-20100811 > Upgrade ruby-1.8.7.248_2,1 to ruby-1.8.7.248_3,1 > Upgrade sqlite3-3.6.23.1_1 to sqlite3-3.6.23.1_2 > Upgrade freetype2-2.4.1 to freetype2-2.4.2 > Upgrade ghostscript8-nox11-8.71_4 to ghostscript8-nox11-8.71_5 > Install print/cups-image > Install print/cups-client > Install security/gnutls > Upgrade bison-2.4.1_1,1 to bison-2.4.3,1 > Upgrade ddclient-3.8.0 to ddclient-3.8.0_1 > Upgrade nginx-devel-0.8.48 to nginx-devel-0.8.49 > Upgrade phpMyAdmin-3.3.5 to phpMyAdmin-3.3.5.1 > > ===>>> Proceed? y/n [y] > > I think this is an issue because ghostscript is a build dependency of > en-freebsd-doc (indirectly: textproc/docproj-jadetex > > textproc/docproj > print/ghostscript8). Thus, the new documentation > tools will be built after the new documentation is built with the old > tools. The case you're describing more generally is: parent port: out of date \ child port: up to date \ grandchild port: out of date This is exact scenario that I left the -t option in the code to handle, and is the only one where I know for sure that it's valid and appropriate. Unfortunately it's nearly impossible for portmaster to detect this situation without -t, and using it routinely has other nasty side effects. The only thing I can suggest at this point is to try -at and see if that works for you. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso