From owner-freebsd-stable@FreeBSD.ORG Thu Feb 28 23:46:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17FFA1065672 for ; Thu, 28 Feb 2008 23:46:42 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id E99A78FC17 for ; Thu, 28 Feb 2008 23:46:41 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id E1D3323ABA45; Thu, 28 Feb 2008 15:46:41 -0800 (PST) Received: from relay14.apple.com (unknown [127.0.0.1]) by relay14.apple.com (Symantec Mail Security) with ESMTP id C9BD528089; Thu, 28 Feb 2008 15:46:41 -0800 (PST) X-AuditID: 11807134-a3beebb0000032fc-b6-47c747e17bc5 Received: from cswiger1.apple.com (cswiger1.apple.com [17.214.13.96]) by relay14.apple.com (Apple SCV relay) with ESMTP id A9C192808A; Thu, 28 Feb 2008 15:46:41 -0800 (PST) Message-Id: From: Chuck Swiger To: Marko Lerota In-Reply-To: <867igo3cih.fsf@zid.claresco.hr> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 28 Feb 2008 15:46:41 -0800 References: <867igo3cih.fsf@zid.claresco.hr> X-Mailer: Apple Mail (2.919.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-stable@freebsd.org Subject: Re: Upgrading to 7.0 - stupid requirements 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: Thu, 28 Feb 2008 23:46:42 -0000 On Feb 28, 2008, at 3:08 PM, Marko Lerota wrote: > In http://www.freebsd.org/releases/7.0R/announce.html says > > Updating Existing Systems >> An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes >> a major version upgrade, so no matter which method you use to update >> an older system you should reinstall any ports you have installed on >> the machine. This will avoid binaries becoming linked to inconsistent >> sets of libraries when future port upgrades rebuild one port but not >> others that link to it. This can be done with: > > # portupgrade -faP > > etc... > > Why!!! The comment above tells you: "This will avoid binaries becoming linked to inconsistent sets of libraries when future port upgrades rebuild one port but not others that link to it." > Do you know how much time I have to spend with my PC to reinstall > all of this programs from ports? Only openoffice takes one day! And > where > is Gnome and such...There must be other way...I would not reinstall my > packages ;) Sure, you could stick with 6.3 for quite some time. > Then the servers. Why should I reinstall all my databases and such? > I always > liked that FreeBSD base (OS) is separated from packages. And no > matter what I > do with the packages, my OS will always work. I don't want dependency > hell like in Linux. Now you are telling me that my database might > not work > after upgrade to a new version. Is that it? Not exactly. The 6.x binaries will continue to work just fine under 7.0, so long as you don't recompile any of the libraries they are using. However, as soon as you start upgrading anything, you will end up with programs trying to pull in the 6.x and 7.x version of libc etc, and that will cause problems. Note that the portupgrade command given above will try to download precompiled binaries where available, rather than requiring you to compile everything locally. -- -Chuck