Date: Sun, 10 Nov 2002 20:53:40 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: sheldonh@starjuice.net Cc: eischen@pcnet1.pcnet.com, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021110.205340.48499499.imp@bsdimp.com> In-Reply-To: <20021109104527.GD347@starjuice.net> References: <20021108.142609.112624839.imp@bsdimp.com> <Pine.GSO.4.10.10211081806220.10745-100000@pcnet1.pcnet.com> <20021109104527.GD347@starjuice.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20021109104527.GD347@starjuice.net>
Sheldon Hearn <sheldonh@starjuice.net> writes:
: If the final word on this whole issue is "You can't run binaries
: compiled for 4.x-RELEASE on 5.x-RELEASE" then we should start puckering
: up.
:
: Developers tend to remember these things and you don't have to screw
: them too many times before they remove FreeBSD downloads from their web
: sites and replace them with a brief message explaining that "We don't
: have time to cope with FreeBSD's disregard for backward compatibility."
:
: At that point, whining about how they shouldn't have been fiddling with
: these symbols in the first place is bound to be a fruitless exercise.
This is why I put __sF back, and made sure that 4.x had the right
'forward compatible' libraries. It is also why I backported the
__std{in,out,err}p symbols. I hope that minor incompatibility within
a minor release is offset by __sF not being referencede by any more
libraries.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021110.205340.48499499.imp>