From owner-freebsd-stable@FreeBSD.ORG Wed Aug 23 23:41:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC01716A4DE for ; Wed, 23 Aug 2006 23:41:31 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F2EB43D45 for ; Wed, 23 Aug 2006 23:41:30 +0000 (GMT) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.13.6/8.13.6) with ESMTP id k7NNfSHC002496 for ; Thu, 24 Aug 2006 01:41:28 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.13.6/8.13.6/Submit) id k7NNfScs002495 for freebsd-stable@freebsd.org; Thu, 24 Aug 2006 01:41:28 +0200 (CEST) (envelope-from byshenknet) Date: Thu, 24 Aug 2006 01:41:28 +0200 From: Greg Byshenk To: freebsd-stable Message-ID: <20060823234128.GM633@core.byshenk.net> References: <5B7BD83A-6316-4C20-903E-B5D66D4F2642@khera.org> <44EB5354.6070007@paladin.bulgarpress.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on core.byshenk.net Subject: Re: 5.5 to 6.1 upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2006 23:41:31 -0000 On Tue, Aug 22, 2006 at 12:23:00PM -0700, Chuck Swiger wrote: > In practice, however, pretty much all software nowadays depends on > shared libraries, so it's reasonable to do a "pkg_delete -a" after > upgrading to a new major version of FreeBSD, and then reinstall all > of the ports you use once you've finished upgrading. Run "pkg_info" > before the upgrade and keep track of this output to help you remember > what ports you've got installed... As a possible point of clarification, my comments earlier (and, I suspect similar comments of others) were not meant to imply that one should not rebuild ports after a major upgrade, but only that one need not do so _before_ upgrading. [...probably ... it worked for me ... YMMV ... if it is a critical package, then it wouldn't hurt to rebuild it first ... usw.] -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL