From owner-freebsd-ports@FreeBSD.ORG  Tue Apr 25 20:11:45 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 E49C016A4F1
	for <freebsd-ports@freebsd.org>; Tue, 25 Apr 2006 20:11:45 +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 672F643D53
	for <freebsd-ports@freebsd.org>; Tue, 25 Apr 2006 20:11:45 +0000 (GMT)
	(envelope-from hans@lambermont.dyndns.org)
Received: by lambermont.dyndns.org (Postfix, from userid 1001)
	id 61E5C22E668; Tue, 25 Apr 2006 22:11:44 +0200 (CEST)
Date: Tue, 25 Apr 2006 22:11:44 +0200
To: Ion-Mihai Tetcu <itetcu@people.tecnik93.com>
Message-ID: <20060425201144.GB4435@leia.lambermont.dyndns.org>
References: <20060425154800.GB1351@leia.lambermont.dyndns.org>
	<444E4624.6070509@vonostingroup.com>
	<20060425182639.GC1351@leia.lambermont.dyndns.org>
	<20060425214257.6648ca76@it.buh.tecnik93.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060425214257.6648ca76@it.buh.tecnik93.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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2006 20:11:46 -0000

Ion-Mihai Tetcu wrote:

> 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).
> 
> If you can build  your ports on an non-production server, use
> portugrade -PP with modified package site in pkgtools.conf

Ah yes, that avoids using pkg_add and it's 200-packages-at-a-time limit.

I'm also looking into other-than-portupgrade ports tree tools, does
anyone know a way to accomplish the equivalent of portupgrade -PP ?

> If you can afford that non-production server the fastest way is to
> delete all installed packages and build them all from scratch.

Which is exactly what I did :) Still took me almost a week.

regards,

-- Hans Lambermont