Date: Wed, 23 Jan 2013 20:44:51 -0800 (PST) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: freebsd-ports@freebsd.org Subject: Re: portmaster -w -r (pcre & icu): how to avoid redundant rebuilding? Message-ID: <1359002691.17702.YahooMailClassic@web164002.mail.gq1.yahoo.com> In-Reply-To: <CAN6yY1vmYxkCb9RtVQn0SgBsA9VFv25GTC-3ES55k_di=P7QNw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Reply is at the bottom... --- On Wed, 1/23/13, Kevin Oberman <kob6558@gmail.com> wrote: From: Kevin Oberman <kob6558@gmail.com> Subject: Re: portmaster -w -r (pcre & icu): how to avoid redundant rebuildi= ng? To: "Thomas Mueller" <mueller6724@bellsouth.net> Cc: "Joseph A. Nagy, Jr" <jnagyjr1978@gmail.com>, freebsd-ports@freebsd.org Date: Wednesday, January 23, 2013, 6:04 PM On Wed, Jan 23, 2013 at 3:58 AM, Thomas Mueller <mueller6724@bellsouth.net> wrote: > >> On 01/22/13 06:26, Thomas Mueller wrote: >> >I see in the UPDATING file that I need to rebuild all ports that depend= on >> >pcre and icu: > >> >portmaster -w -r pcre >> >and >> >portmaster -w -r icu >> >(I don't need -f ?) > >> >How do I do this without rebuilding the same ports twice? > >> >I am on pkgng, so I can use >> >pkg info -r icu >> >and same for pcre to list ports depending on icu and pcre (long lists). > >> >I just updated, from source, to: > > >> >FreeBSD amelia2 9.1-STABLE FreeBSD 9.1-STABLE #14 r245542: Tue Jan 22 >> >03:00:31 UTC 2013=A0 =A0=A0=A0root@amelia2:/usr/obj/usr/src/sys/SANDY= =A0 amd64 > >> >Tom > >> I've not had any luck with avoiding redundant rebuilding as pcre and icu >> updates aren't sent out at the same time. Perhaps someone can say if I'm >> off my rocker, has anyone tried issuing 'portmaster -w -r icu pcre'? >> Perhaps that would avoid the redundant rebuilds? > >> Of course that would only work if one waits for both updates to come out= . > >> -- >> Yours in Christ, > >> Joseph A Nagy Jr > > I could possibly make lists of ports that depend on pcre and icu using > > pkg info -r icu (and also pcre, redirecting to files) > > Then I could try > portmaster -w -r icu -r pcre > or do I need to use -w twice? > > Then I could see what ports it would build, say n when asked if I wanted = to rebuild those ports, assuming there would be config dialogs along the li= ne. > > Then I would run the portmaster command again with |& tee portm.log at th= e right end, see if I like what would be built before answering y. > > I would be able to login to another virtual terminal to examine portm.log= file at the early stage when asked whether to rebuild the ports >My standard answer (and huge time-saver) is to install sysutils/bsdasminscripts and do the following. This example is for pcre and icu >% pkg_libchk -o | grep -E "libpcre|libicu" | cut -d: -f1 | sort | uniq > pcre-updates.txt % portmaster `cat pcre-updates.txt` >This will only update any port once and will only update ports that really need it. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" If you'd rather put off most of the rebuilds until they bump anyway, simply= maybe run the ports you want to use in the interim out of X, say an editor= (gtk2) run without X may show only one of its dependencies need actual reb= uilding.=A0=20 Not recommended as a general procedure for most systems maybe, but somethin= g to keep in mind... it shows in some instances more information than simply ldd'ing the binary, resulting i= n less downtime of the desktop or whatever.=20 J. Bouquet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1359002691.17702.YahooMailClassic>