From owner-freebsd-questions@FreeBSD.ORG Sat May 19 11:50:50 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 133B116A402 for ; Sat, 19 May 2007 11:50:50 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id E1C3613C457 for ; Sat, 19 May 2007 11:50:49 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 6D0065193B for ; Sat, 19 May 2007 07:50:44 -0400 (EDT) Date: Sat, 19 May 2007 12:50:41 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070519125041.54e7da47@gumby.homeunix.com.> In-Reply-To: <20070518132807.Q17258@duane.dbq.yournetplus.com> References: <20070516182846.C34584@duane.dbq.yournetplus.com> <464BCE1A.4020400@infracaninophile.co.uk> <20070517102831.O61920@duane.dbq.yournetplus.com> <20070518141045.490c80be@gumby.homeunix.com.> <20070518132807.Q17258@duane.dbq.yournetplus.com> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: amd64 FreeBSD Release 5.5 -> 6.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2007 11:50:50 -0000 On Fri, 18 May 2007 13:31:52 +0000 (UTC) Duane Hill wrote: > On Fri, 18 May 2007, RW wrote: > > > On Thu, 17 May 2007 10:39:35 +0000 (UTC) > > Duane Hill wrote: > > > >> On Thu, 17 May 2007, Matthew Seaman wrote: > >> > > > >>> You should be able to upgrade the system by a routine buildworld, > >>> buildkernel ... type operation, but beware that you will need to > >>> recompile all of your ports because of potential shlib version > >>> clashes. Ports from 5.5 will still work on 6.2, but later trying > >>> to update them piecemeal can lead to misery. > >> > >> I'm using portupgrade. So I will use the switches force a reinstall > >> and to act on everything that depends on the reinstalled port > >> (-fr). > >> > > > > > > That wont do anything useful as there is nothing for the -r to work > > with after a base-system upgrade. > > > > The best way to upgrade all ports with portupgrade is to do it by > > datestamp like this: > > > > portupgrade -f '<2007-05-18 14:00' > > What about: > > portupgrade -afR > > Wouldn't that force everything including ports that depend on the one > being reinstalled? If you use the datestamp instead of -a, you can stop and start the build.