From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 20:27:24 2005 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 9E4FF16A41F for ; Thu, 20 Oct 2005 20:27:24 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59AC643D5A for ; Thu, 20 Oct 2005 20:27:24 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 34D6C1A3C1A; Thu, 20 Oct 2005 13:27:24 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9006E5149E; Thu, 20 Oct 2005 16:27:23 -0400 (EDT) Date: Thu, 20 Oct 2005 16:27:23 -0400 From: Kris Kennaway To: Vivek Khera Message-ID: <20051020202723.GA25790@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 20 Oct 2005 20:27:24 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 20, 2005 at 03:20:52PM -0400, Vivek Khera wrote: >=20 > On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote: >=20 > >Wat is the best way to get the cleanest FreeBSD-6.x system without > >installing from scratch? Recompile each port? Or use the > >COMPAT_FREEBSD5 layer? > > > > >=20 > this is a different question than you asked before... the =20 > COMPAT_FREEBSD5 will allow your existing binaries to continue to =20 > run. you can leave this on while you run "portupgrade -f -a" to =20 > recompile all your ports, then you can take it out... and remove all =20 > the compat libraries sitting around if you care to do so. >=20 > personally, I don't see the point of doing that. just let your ports =20 > naturally get replaced as they are upgraded due to version bumps and =20 > such. This isn't enough, because you'll still get new 6.0 ports compiled against old 5.x libraries and the situation I detailed in my previous email. If you want to use continue to ports after upgrading to a new major release, you *must* first recompile your old ports to avoid those problems. Kris --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDV/2rWry0BWjoQKURAga+AJ9AuPyh+ZMxJn9RH3O69RlUhFIHUwCgsrNP wP+KJxPJBidISZ1N/m885Xw= =Ss6A -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc--