From owner-freebsd-stable Mon Nov 13 20:21:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2BCD537B479; Mon, 13 Nov 2000 20:21:39 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA09146; Mon, 13 Nov 2000 20:21:38 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAE4LbH42963; Mon, 13 Nov 2000 20:21:37 -0800 (PST) (envelope-from jdp) Date: Mon, 13 Nov 2000 20:21:37 -0800 (PST) Message-Id: <200011140421.eAE4LbH42963@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: asami@freebsd.org Subject: Re: libc shlib version In-Reply-To: References: <31309.974061923@winston.osd.bsdi.com> <200011131727.eADHR8c42388@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Satoshi - Ports Wraith - Asami wrote: > * From: John Polstra > > * If it contains a new libc, that seems like the real problem > * to me. It's always risky to use new libs (especially libc) with an > * old kernel. > > New ports and packages didn't work with the old libc because someone > moved stuff from libxpg4 to libc without changing the version numbers. > Putting it in the upgrade kit was the only way to let 4.0R people use > ports-current. That sounds like a good reason to me. Maybe you should have included a kernel in the upgrade kit too ... ;-) > Maybe I should have insisted that the libc version change back then. > I really wish we could keep the two version numbers from a.out, so I > don't have to worry about stuff like this. :< Sorry! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message