Date: Sun, 19 Oct 2003 16:24:03 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: current@freebsd.org Subject: Re: __fpclassifyd problem Message-ID: <20031019232403.GA33279@troutmask.apl.washington.edu> In-Reply-To: <20031019224858.GA64932@rot13.obsecurity.org> References: <3F92E129.10307@veidit.net> <20031019204629.GC49466@rot13.obsecurity.org> <3F92FC99.8010802@freebsd.org> <20031019221341.GA32851@troutmask.apl.washington.edu> <20031019224858.GA64932@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 19, 2003 at 03:48:58PM -0700, Kris Kennaway wrote: > On Sun, Oct 19, 2003 at 03:13:41PM -0700, Steve Kargl wrote: > > > I sent in an email *along time ago* about this type > > of problem. See the fallout due to revision 1.24 > > of lib/libc/stdio/findfp.c. IMHO, all shared libraries > > versions should have been bumped in going from 4.x to > > 5.0. > > You don't want to do it before you have to, because this creates more > pain for people when you make a change that breaks backwards compat > (given the policy/preference of only bumping once per major release). > > I'm working on a script that will detect the kind of backwards > compatibility breakage we're seeing here by comparing the symbols in > 4.x and 5.x versions of libraries with the same major revision. We > can then run this once a day/week/whatever somewhere to catch these > problems as soon as they occur in future. > You and I participated in the first go around in the library versioning problem. For one of my attempts to discuss this problem, see http://www.freebsd.org/cgi/getmsg.cgi?fetch=1981830+1986079+/usr/local/www/db/text/2002/freebsd-current/20021103.freebsd-current -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031019232403.GA33279>