From owner-freebsd-current@FreeBSD.ORG Sun Oct 19 16:24:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 485CD16A4B3; Sun, 19 Oct 2003 16:24:05 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49A8A43FB1; Sun, 19 Oct 2003 16:24:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h9JNO4OH033407; Sun, 19 Oct 2003 16:24:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)h9JNO3xQ033406; Sun, 19 Oct 2003 16:24:03 -0700 (PDT) (envelope-from sgk) Date: Sun, 19 Oct 2003 16:24:03 -0700 From: Steve Kargl To: Kris Kennaway Message-ID: <20031019232403.GA33279@troutmask.apl.washington.edu> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031019224858.GA64932@rot13.obsecurity.org> User-Agent: Mutt/1.4.1i cc: re@freebsd.org cc: current@freebsd.org Subject: Re: __fpclassifyd problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Oct 2003 23:24:05 -0000 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