Date: Mon, 13 Nov 2000 20:21:37 -0800 (PST) From: John Polstra <jdp@polstra.com> To: stable@freebsd.org Cc: asami@freebsd.org Subject: Re: libc shlib version Message-ID: <200011140421.eAE4LbH42963@vashon.polstra.com> In-Reply-To: <vqc8zqnmqkb.fsf@silvia.hip.berkeley.edu> References: <31309.974061923@winston.osd.bsdi.com> <vqcd7g09vtq.fsf@silvia.hip.berkeley.edu> <200011131727.eADHR8c42388@vashon.polstra.com> <vqc8zqnmqkb.fsf@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <vqc8zqnmqkb.fsf@silvia.hip.berkeley.edu>, Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> wrote: > * From: John Polstra <jdp@polstra.com> > > * 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011140421.eAE4LbH42963>