Date: Wed, 29 Sep 2004 17:49:14 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: deischen@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP: Library version number bumps Message-ID: <20040929.174914.05878370.imp@bsdimp.com> In-Reply-To: <Pine.GSO.4.43.0409291006430.13426-100000@sea.ntplx.net> References: <20040929123100.GA600@electra.cse.Buffalo.EDU> <Pine.GSO.4.43.0409291006430.13426-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 time.
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?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040929.174914.05878370.imp>