Date: Sat, 21 Aug 2010 17:49:32 -0700 From: Rob Farmer <rfarmer@predatorlabs.net> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: portmaster and build depends Message-ID: <AANLkTikdFSHe3pDr2dF6r9jbKaTo-48Rk%2B%2BK7gfhObwP@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1008211457010.1942@qbhto.arg> References: <AANLkTim0GwMmPntpOb-F8uQ66F38Ucmu19RqhyQqWFJL@mail.gmail.com> <alpine.BSF.2.00.1008211457010.1942@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 21, 2010 at 3:03 PM, Doug Barton <dougb@freebsd.org> 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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikdFSHe3pDr2dF6r9jbKaTo-48Rk%2B%2BK7gfhObwP>