From owner-freebsd-ports@FreeBSD.ORG Tue Apr 25 18:40:47 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9266016A401 for ; Tue, 25 Apr 2006 18:40:47 +0000 (UTC) (envelope-from laszlof@vonostingroup.com) Received: from ritamari.vonostingroup.com (ritamari.vonostingroup.com [216.144.193.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FDC943D45 for ; Tue, 25 Apr 2006 18:40:47 +0000 (GMT) (envelope-from laszlof@vonostingroup.com) Received: from adsl-68-72-248-38.dsl.sfldmi.ameritech.net ([68.72.248.38] helo=[192.168.1.33]) by ritamari.vonostingroup.com with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FYSTp-000D5T-Iv; Tue, 25 Apr 2006 14:41:45 -0400 Message-ID: <444E6D2A.8090001@vonostingroup.com> Date: Tue, 25 Apr 2006 14:40:42 -0400 From: Frank Laszlo User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Hans Lambermont References: <20060425154800.GB1351@leia.lambermont.dyndns.org> <444E4624.6070509@vonostingroup.com> <20060425182639.GC1351@leia.lambermont.dyndns.org> In-Reply-To: <20060425182639.GC1351@leia.lambermont.dyndns.org> X-Enigmail-Version: 0.93.2.0 OpenPGP: url=http://www.franksworld.org/~laszlof/keys/0x0B3FCA4B.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ritamari.vonostingroup.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - vonostingroup.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-ports@freebsd.org Subject: Re: libtool upgrade, entry 20060223 in UPDATING X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 18:40:47 -0000 the '-p' argument for portupgrade will build packages on your staging server, these packages can then be moved over to the production machine to be installed. Downtime should be minimal. __________________________________________________ Frank Laszlo System Administrator The VonOstin Group Email: laszlof@tvog.net WWW: http://www.vonostingroup.com Mobile: 248-863-7584 Hans Lambermont wrote: > Frank Laszlo wrote: > > >> Hans Lambermont wrote: >> >>> The 20060223 entry in UPDATING suggests that the only reliable way of >>> upgrading a system is to remove all packages and reinstalling from >>> scratch. >>> > ... > >>> Next to that I'd like to hear from others how to accomplish this >>> all-ports upgrade on servers where one wants the downtime to be >>> minimal. >>> >> portupgrade -afp isnt good enough? >> > > No, I want to have minimal downtime of the server. When using > 'portupgrade -afp' the system is in flux for almost a week. I want to > avoid that, and the only way I know how to avoid that is to use a > staging and build server (at least that's the idea). > > Besides, the 20060223 entry in UPDATING mentions : > > Unfortunately, there is no simple upgrade path. Short of removing > all packages and reinstalling from scratch, the only other viable > alternative would be careful use of portupgrade. > > I assume -afp is not 'careful use of portupgrade'. It follows with : > > Given the large > number of different ways in which libtool is used by other ports > in the tree, this is a process that is likely to vary considerably > from system to system, and as such, folks should be very mindful > of running automatic updating software, such as portupgrade, making > extensive use of the -n flag (and equivalents for other updaters) > to see what will actually be rebuilt, before actually performing > the upgrade. > > Which makes me wonder what to look for when using '-n', how to decide > whether to update a port or not ? > > -- Hans Lambermont >