Date: Wed, 29 Sep 2004 17:44:17 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP: Library version number bumps Message-ID: <20040930004417.GA49094@xor.obsecurity.org> In-Reply-To: <Pine.GSO.4.43.0409292016080.16453-100000@sea.ntplx.net> References: <20040929.174914.05878370.imp@bsdimp.com> <Pine.GSO.4.43.0409292016080.16453-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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: <Pine.GSO.4.43.0409291006430.13426-100000@sea.ntplx.net> > > Daniel Eischen <deischen@freebsd.org> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040930004417.GA49094>