From owner-freebsd-ports@FreeBSD.ORG  Wed Aug 16 10:10:53 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 2DC0C16A4E0
	for <freebsd-ports@FreeBSD.org>; Wed, 16 Aug 2006 10:10:53 +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 A030243D5F
	for <freebsd-ports@FreeBSD.org>; Wed, 16 Aug 2006 10:10:52 +0000 (GMT)
	(envelope-from hans@lambermont.dyndns.org)
Received: by lambermont.dyndns.org (Postfix, from userid 1001)
	id 56EEC22DDA2; Wed, 16 Aug 2006 12:10:51 +0200 (CEST)
Date: Wed, 16 Aug 2006 12:10:51 +0200
To: freebsd-ports@FreeBSD.org
Message-ID: <20060816101051.GA67212@leia.lambermont.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
From: hans@lambermont.dyndns.org (Hans Lambermont)
Cc: 
Subject: libtool upgrade question (UPDATING/20060223)
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: Wed, 16 Aug 2006 10:10:53 -0000

Hi,

I have a question about a ports upgrade method as mentioned in the
20060223 libtool entry in UPDATING.

The entry 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.  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.

I'm wondering what the 'careful use of' really means, more specifically
what should one look out for when using the mentioned '-n' ?

regards,
   Hans Lambermont