From owner-freebsd-questions@FreeBSD.ORG Sun Oct 3 11:09:26 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 3EAAF106564A for ; Sun, 3 Oct 2010 11:09:26 +0000 (UTC) (envelope-from freebsd.user@seibercom.net) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id E36868FC15 for ; Sun, 3 Oct 2010 11:09:25 +0000 (UTC) Received: by yxn35 with SMTP id 35so1915418yxn.13 for ; Sun, 03 Oct 2010 04:09:25 -0700 (PDT) Received: by 10.101.97.8 with SMTP id z8mr3694489anl.209.1286104164724; Sun, 03 Oct 2010 04:09:24 -0700 (PDT) Received: from scorpio.seibercom.net (cpe-071-077-039-064.nc.res.rr.com [71.77.39.64]) by mx.google.com with ESMTPS id i25sm6589842anh.37.2010.10.03.04.09.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 03 Oct 2010 04:09:24 -0700 (PDT) Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: FreeBSD.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 7CBACE54835 for ; Sun, 3 Oct 2010 07:09:22 -0400 (EDT) Date: Sun, 3 Oct 2010 07:09:21 -0400 From: Jerry To: FreeBSD Message-ID: <20101003070921.6159f9ea@scorpio> In-Reply-To: <4ca853f7.u8GtTT6YlSKwZwFM%mueller6727@bellsouth.net> References: <4ca853f7.u8GtTT6YlSKwZwFM%mueller6727@bellsouth.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEX3/uPVnZf2/v9ejGkqHB74++H///+cHCT3m6cgqYvfAAACbElEQVQ4jWXTQW/bIBQAYJLJuRMn8TVCss9zTdrrXJ6bHe1Ej/bossF9EpJ3nbapf3sP8JxOQ4qV8OU9HvjBROWcYNlKHtxlQ1/huBaOBiMwQtgHhbokMLIT76Acps5hvy61+6WsjkCZzNEW0+fcQ7Nl5uoPCegjjjhN5/MEABd89k9hXkQoX6cwPIDKCt8tYG5wpmdrxAyuolTPqpiVoEpVCWvl6e00RAD4JBJQnO4lvv0O4Cnd3WUGevYNFohxFYAy7jCCtW39LaQK8BgDAgiHVinVJlCiFKlcqgEHfwb1EuG+DwFGMO3oCIuJIEYoa8KJECBB+UBldgm0MQmEGz7GQr8XYRPKzYNO1zZ8mgdAu4BG5Ke/4KFboM8458UScViAAvYD93OAsu+Bc3zxCU7ZAjT74+dQv9K7oO0d1wuscop48Pc50O5bcVwgGzh/mXzaizJuAWERh8k3eaxKmxu4kV1p2XOEg3i3c8M+EKR93P0D1KATpC55vMHaGqFf5f/AwhlrhHgg8DTezopt6I3o3Qx4q4q6YaPxK8RxcClXeFGhTTS++QR6TS/oBs7l4WhzuNMubZG6hIBkF4qqZVdWczIqSrjKVF/i4o26IP2oElBGFy5CXKSnf6UWDTC6zKSqoAvzsakjjBvdzLKnmxdhY8eRsX7VSCUBdgD1hVJpx6y2OOS1DNDILYmqdWUJ+oHvd0rRvAqX5kpxQMR6yxHzPV6VlPFyWE7LKc36keNQI64gLP8Ybgtmg+zYuBl4fuI8VqW2RqDGE8Uzu7GxGa803whDdxx3bSZbRhfQUSxvmnpLZWpRFqHz7v8AvsBe0S1zv9UAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Massive portupgrade without being interrupted by configuration screens? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2010 11:09:26 -0000 On Sun, 03 Oct 2010 09:59:19 +0000 Thomas Mueller articulated: > >From "Elias Chrysocheris" : > > > If you are sure that the default configuration settings are OK for > > you, then one way is to perform a portupgrade with the switches > > --batch --yes, like portupgrade --batch --yes -a > > > This will assume that the default settings are those you like and > > will not ask you anything about configuration screens e.t.c. > > > Elias > > Idea is that I might want to configure some of the options, so I > can't use --batch=YES unless I configure all options beforehand, > meaning I have to find what ports are to be upgraded and which of > those have user-selectable options. > > Are there any adverse side effects if I use portupgrade some of the > time, and postmaster other times? > > Reason for wanting to do all "make config"s beforehand is not only > efficiency and ability to run unattended, but the ability to recover > from a typo at the config dialog interface, which can be confusing, > on when to press spacebar, tab, enter, up- and down-arrows. > > Now I see in UPDATING file, date 20100915, that lang/perl5.12 has > been updated to 5.12.2. > > 20100915: > AFFECTS: users of lang/perl5.12 > AUTHOR: skv@FreeBSD.org > > lang/perl5.12 has been updated to 5.12.2. You should update > everything that depends on perl. The easiest way to do that is to use > "perl-after-upgrade" script supplied with lang/perl5.12. > Please see its manual page for details. > > If you want to switch to lang/perl5.12 from lang/perl5.{8,10} please > follow instructions in the entry 20100715 in this file. > > > I only saw this via FreeBSD web site Oct 3 (20101003), after my > original inquiry. Does this mean I have to go through all the > troubles again? > > I already successfully portupgraded Perl to 5.12.2. But I guess I > need to read "perl-after-upgrade" script before doing anything > (including panicking?). If you were to use 'portmanager' with its '-p' option, it would rebuild all ports that depend on the new version of Perl as well as any ports that depended on those ports as well. It would insure that the dependency links were fully updated. There is then no need to run the superfluous "perl-after-upgrade' script; although, you are free to do so if you so desire. -- Jerry ✌ FreeBSD.user@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Hartley's First Law: You can lead a horse to water, but if you can get him to float on his back, you've got something.