Date: Thu, 28 Feb 2008 17:11:57 -0800 From: Bakul Shah <bakul@bitblocks.com> To: Kris Kennaway <kris@FreeBSD.org> Cc: Marko Lerota <mlerota@iskon.hr>, freebsd-stable@freebsd.org Subject: Re: Upgrading to 7.0 - stupid requirements Message-ID: <20080229011157.3C4535B3B@mail.bitblocks.com> In-Reply-To: Your message of "Fri, 29 Feb 2008 01:57:32 %2B0100." <47C7587C.7080202@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Feb 2008 01:57:32 +0100 Kris Kennaway <kris@FreeBSD.org> wrote: > Bakul Shah wrote: > > On Fri, 29 Feb 2008 00:54:55 +0100 Kris Kennaway <kris@FreeBSD.org> wrote: > >> portupgrade -faP requests to reinstall everything from precompiled > >> packages. It will only fall back to compiling them locally if the > >> package is unavailable (e.g. for legal reasons). > >> > >> Second, the reason for this requirement is explained in the > >> announcement. In fact, it has *always* been required to recompile ports > >> when moving to a new major release of FreeBSD, for guaranteed correct > >> operation when some of the ports are updated later on. > > > > Er... Can't one run old binaries after installing one or more > > of usr/ports/misc/compat-[3456]x -- that has not changed, has > > it? > > No, it has not. Excellent! I was getting worried a bit :-) > As I've tried to explain, the difficulty is when you start recompiling > parts of them, e.g. a shared library used by other ports. Understood. Hmm... If prior to any recompile such a shared lib was copied to a compat dir (based on the most recent shared lib *it* depends on), programs relying on it would continue working. Thanks for the explanation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080229011157.3C4535B3B>