From owner-freebsd-ports@FreeBSD.ORG Thu Jan 24 02:04:18 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 95EE42F9 for ; Thu, 24 Jan 2013 02:04:18 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by mx1.freebsd.org (Postfix) with ESMTP id 52F7AE37 for ; Thu, 24 Jan 2013 02:04:18 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id rl6so5204897pac.29 for ; Wed, 23 Jan 2013 18:04:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=KM9jOrB05OuN8WfFECof2cCfh/5IaWpjUBmJBpGx4R4=; b=nM2h+bGmaq0r5MWOJEEIZBWqNjjPhIjMLeJBCEbfLcrlCkhHwAMbPXWW487KNrgHPS n1detp4gM9W6O5OPgxJ5ZUSppY4KG8gbnlHB2x4Jg1T841YZlf2eRiahkrFcBWHvUkgF zIxcDqYR+4UsR5eYlEbQCjMlYYgViDvxr9vb1ELeowX40A0+/iwZ6Nz/WnJ82dsLKEzL 7wxyYUNeBjVO+44r4+oGsrwd3lqN6nAxYCZy39/7J3T9HgpbtnEZL7d6upstETOCOMfR Q0sTxbVFEMycga7sOV8x4/WG63NcdsvYS5mwye3tRBIyzplb/QNWdvlO3ttuYXgX/kLS tTGQ== MIME-Version: 1.0 X-Received: by 10.68.252.228 with SMTP id zv4mr33827pbc.17.1358993057750; Wed, 23 Jan 2013 18:04:17 -0800 (PST) Received: by 10.67.2.65 with HTTP; Wed, 23 Jan 2013 18:04:17 -0800 (PST) In-Reply-To: <02.B6.27613.660DFF05@smtp01.insight.synacor.com> References: <02.B6.27613.660DFF05@smtp01.insight.synacor.com> Date: Wed, 23 Jan 2013 18:04:17 -0800 Message-ID: Subject: Re: portmaster -w -r (pcre & icu): how to avoid redundant rebuilding? From: Kevin Oberman To: Thomas Mueller Content-Type: text/plain; charset=UTF-8 Cc: "Joseph A. Nagy, Jr" , freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 02:04:18 -0000 On Wed, Jan 23, 2013 at 3:58 AM, Thomas Mueller 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 root@amelia2:/usr/obj/usr/src/sys/SANDY 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 line. > > Then I would run the portmaster command again with |& tee portm.log at the 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. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com