From owner-freebsd-ports@FreeBSD.ORG Sun Aug 22 00:49:33 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 DC4041065672; Sun, 22 Aug 2010 00:49:33 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8A4DF8FC08; Sun, 22 Aug 2010 00:49:33 +0000 (UTC) Received: by vws7 with SMTP id 7so4952329vws.13 for ; Sat, 21 Aug 2010 17:49:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.126.166 with SMTP id c38mr1980645vcs.52.1282438172691; Sat, 21 Aug 2010 17:49:32 -0700 (PDT) Received: by 10.220.199.202 with HTTP; Sat, 21 Aug 2010 17:49:32 -0700 (PDT) X-Originating-IP: [71.1.133.114] In-Reply-To: References: Date: Sat, 21 Aug 2010 17:49:32 -0700 Message-ID: From: Rob Farmer To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Sun, 22 Aug 2010 00:49:33 -0000 On Sat, Aug 21, 2010 at 3:03 PM, Doug Barton wrote: > 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. >> >> =3D=3D=3D>>> The following actions will be taken if you choose to procee= d: >> =A0 =A0 =A0 Upgrade en-freebsd-doc-20100625 to en-freebsd-doc-20100811 >> =A0 =A0 =A0 Upgrade ruby-1.8.7.248_2,1 to ruby-1.8.7.248_3,1 >> =A0 =A0 =A0 Upgrade sqlite3-3.6.23.1_1 to sqlite3-3.6.23.1_2 >> =A0 =A0 =A0 Upgrade freetype2-2.4.1 to freetype2-2.4.2 >> =A0 =A0 =A0 Upgrade ghostscript8-nox11-8.71_4 to ghostscript8-nox11-8.71= _5 >> =A0 =A0 =A0 Install print/cups-image >> =A0 =A0 =A0 Install print/cups-client >> =A0 =A0 =A0 Install security/gnutls >> =A0 =A0 =A0 Upgrade bison-2.4.1_1,1 to bison-2.4.3,1 >> =A0 =A0 =A0 Upgrade ddclient-3.8.0 to ddclient-3.8.0_1 >> =A0 =A0 =A0 Upgrade nginx-devel-0.8.48 to nginx-devel-0.8.49 >> =A0 =A0 =A0 Upgrade phpMyAdmin-3.3.5 to phpMyAdmin-3.3.5.1 >> >> =3D=3D=3D>>> 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 > =A0 =A0 =A0 =A0\ > =A0 =A0 =A0 =A0 child port: up to date > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0\ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 grandchild port: out of date > > This is exact scenario that I left the -t option in the code to handle, a= nd > 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 situat= ion > 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. Ok, portmaster -at seems to work as expected. However, the problem with this solution is that if -t isn't recommended for routine use, how am I supposed to know when to use it? --=20 Rob Farmer > > > hth, > > Doug > > -- > > =A0 =A0 =A0 =A0Improve the effectiveness of your Internet presence with > =A0 =A0 =A0 =A0a domain name makeover! =A0 =A0http://SupersetSolutions.co= m/ > > =A0 =A0 =A0 =A0Computers are useless. They can only give you answers. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-- Pablo Picasso > >