From owner-freebsd-current@FreeBSD.ORG Thu Sep 30 00:43:53 2004 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 B103A16A4CE; Thu, 30 Sep 2004 00:43:53 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E24143D2F; Thu, 30 Sep 2004 00:43:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id EC64051448; Wed, 29 Sep 2004 17:44:17 -0700 (PDT) Date: Wed, 29 Sep 2004 17:44:17 -0700 From: Kris Kennaway To: Daniel Eischen Message-ID: <20040930004417.GA49094@xor.obsecurity.org> References: <20040929.174914.05878370.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: kensmith@cse.Buffalo.EDU cc: tjr@freebsd.org cc: "M. Warner Losh" cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP: Library version number bumps 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: Thu, 30 Sep 2004 00:43:53 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 29, 2004 at 08:36:45PM -0400, Daniel Eischen wrote: > On Wed, 29 Sep 2004, M. Warner Losh wrote: >=20 > > In message: > > Daniel Eischen writes: > > : This has been mentioned before, but when breaking (or potentially > > : breaking) ABI, can we bump the version numbers to libfoo.YYYYMMDD? > > : Once release comes, we can move them back to SHLIB_MAJOR + 1 (or > > : even decide to keep them at SHLIB_MAJOR if ABI wasn't really broken). > > : This helps folks running HEAD so they can update their ports over tim= e. > > > > In a lot of respects I like this idea. However, the unanswered > > question would be how to implement it. The bumps are easy to do (the > > version number is basically meaningless), but frequeny bumps have > > issues as well. Laying those aside for the moment, my concern is how > > do we do the 'one release comes' part there. How do we know if they > > are binary compatible or not? Wouldn't this tend to encourage people > > to make binary incompatible libraryes? >=20 > It doesn't solve the current problem of knowing if changes > break ABI. It is also still up to the committers to both > avoid introducing any uncessary ABI breakages and to review > other committers' changes. That hasn't worked very well during the 5.x branch, as the current thread (and previous iterations of it) show. All I was able to look for were incompatible changes to the symbol table; other types of breakage like incompatible changes to function interfaces and data structures are much more difficult to detect. Kris --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBW1bhWry0BWjoQKURAqWZAJ0SEBZdCr76GxzuxHqmGLPUwT/ggACgir/A tZ091Kvhfwy6/WIn2ndohAI= =Wdby -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--