From owner-freebsd-questions@FreeBSD.ORG Sat Oct 2 14:49:51 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D6A2106564A for ; Sat, 2 Oct 2010 14:49:51 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id C691D8FC1B for ; Sat, 2 Oct 2010 14:49:50 +0000 (UTC) Received: by wwi18 with SMTP id 18so16678wwi.1 for ; Sat, 02 Oct 2010 07:49:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=g9XVMLCDUBi74zfGzkILetN6yeZrZYms3d7FPktGTPk=; b=MxRzqtJP/E0baSLujj9qlypH0ZUe40BhEm5SD374UfJPv8GwT12vYK1irocOMcYObM Vr9N5ejVetD48fynWcxNB8Tbl0hw7ZNl7+t6Gaxn/ylAfoU9b481Mt5yAYkktLABWPkx Ektia0nPaUadCg6RGlkNK7Go6Ym1fKroCXUJM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BSard1lIiOImBolaP/+NTOJ9RXf2EfsLfdoRDN9dc0KwcSXNhvhV3Lz67YjScMyGS8 XgOOaFCB4xFQwC6CjnSPs1j+xRz5fxZL66Dul+Pex2GJLh4F0ANP6y5vKoDKcIsE9md4 AOrgrEzi1eK5A0HdHqi8RCLgYPcvmhOnbHZP0= MIME-Version: 1.0 Received: by 10.216.50.18 with SMTP id y18mr3269296web.113.1286030989869; Sat, 02 Oct 2010 07:49:49 -0700 (PDT) Received: by 10.216.133.133 with HTTP; Sat, 2 Oct 2010 07:49:49 -0700 (PDT) In-Reply-To: <4ca708f4.svuMWmkOCHSjxBDf%mueller6727@bellsouth.net> References: <4ca708f4.svuMWmkOCHSjxBDf%mueller6727@bellsouth.net> Date: Sat, 2 Oct 2010 09:49:49 -0500 Message-ID: From: Brandon Gooch To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Massive portupgrade without being interrupted by configuration screens? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2010 14:49:51 -0000 On Sat, Oct 2, 2010 at 5:27 AM, Thomas Mueller wrote: > How can one do a massive portupgrade, as with -r or -R, without being int= errupted by options configuration screens for many individual ports? =A0Ide= a is to let it run unattended such as when I might run it starting just bef= ore bedtime. =A0Doing "make config" ahead of time also gives the chance to = recover from a typo at the configuration screen (high risk). > > Best thing I can think of is, using multimedia/ffmpeg as an example, is d= oing a dry run > > portupgrade -Rn multimedia/ffmpeg |& tee -a wouldbe.log > > This would show what other packages would need to be portupgraded and avo= id reconfiguring up-to-date dependencies. =A0Then I would go to each of tho= se directories in the ports tree and run "make config". > > Running "make config-recursive" in /usr/ports/multimedia/ffmpeg would pro= duce configuration screens for all dependencies, including those that are u= p-to-date. > > I tried > > portupgrade -RCn multimedia/ffmpeg |& tee -a wouldbe.log > > but then I got all dependency configuration screens, including those that= were up-to-date, and also the interface didn't work right: I got garbage w= hen trying to respond; it didn't write to the configuration screen but prod= uced non-color garbage to the background. > > Running "make config-recursive" in /usr/ports/multimedia/ffmpeg would con= figure all dependencies, including those that are up-to-date and therefore = not in need of portupgrading, though "make config-recursive" seems appropri= ate for a first build/install of a port. > > But I think there is no perfect way to be sure of doing all "make config"= s in advance, since selectable options could require additional dependencie= s. > > If you try to portupgrade perl to 5.12 and everything that depends on it,= as advised in UPDATING file, date 20100715, you will likely get a lot of c= onfiguration dialog screens: I speak from experience, would surely like a w= ay to do all these "make config"s at the beginning. > > Tom Well, I'm not using portupgrade, but instead ports-mgmt/portmaster: # portmaster --force-config --no-confirm [...] lang/perl5.12 Gets all of the config menus out of the way (--force-config), and doesn't sit waiting for confirmation to proceed with install (--no-confirm). I do this only the first time I build a port, or if I need to change a config option and reinstall. Works for me! -Brandon