Date: Thu, 28 Feb 2008 16:13:43 -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: <20080229001343.C2A455B50@mail.bitblocks.com> In-Reply-To: Your message of "Fri, 29 Feb 2008 00:54:55 %2B0100." <47C749CF.4010501@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? I agree that people *should* recompile but it is not always possible or convenient and in such cases the compat libraries are a good crutch. In face one strong point of freebsd has been (or was) backward compatibility. > This is not FreeBSD-specific advice. It is true on any operating system > when the underlying set of libraries changes in an incompatible way. > However, on FreeBSD this *only* happens betweeen version branches. Almost all commercial OSes provide some degree of backward compatibility; some do much better (such as IBM & SGI).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080229001343.C2A455B50>