From owner-freebsd-ports@FreeBSD.ORG Tue Apr 25 18:26:40 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 6A86F16A400 for ; Tue, 25 Apr 2006 18:26:40 +0000 (UTC) (envelope-from hans@lambermont.dyndns.org) Received: from lambermont.dyndns.org (lambermont.dyndns.org [82.93.47.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E8143D46 for ; Tue, 25 Apr 2006 18:26:39 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id 189A522E668; Tue, 25 Apr 2006 20:26:39 +0200 (CEST) Date: Tue, 25 Apr 2006 20:26:39 +0200 To: Frank Laszlo Message-ID: <20060425182639.GC1351@leia.lambermont.dyndns.org> References: <20060425154800.GB1351@leia.lambermont.dyndns.org> <444E4624.6070509@vonostingroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444E4624.6070509@vonostingroup.com> User-Agent: Mutt/1.4.2.1i From: hans@lambermont.dyndns.org (Hans Lambermont) 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:26:40 -0000 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