On Mon, 2006-04-10 at 16:11 -0700, Justin Erenkrantz wrote:
> Please take a look at how a typical glib, gtk+, etc. apps expose
> glib/gtk+ ABIs. When a glib primative size changes (which has the
> potential of changing in a couple of 2.x.y point releases of glib), so
> does the ABI for that downstream application.
glib provides a consist ABI within major versions. (I dispute that glib
primitive sizes have changed between point releases.) No downstream
library works with both glib 1.x and glib 2.x.
> But, the solution to this is not to create our own internal copy of
> every APR data structure and only expose our 'private' copy - because
> if the APR ABI does indeed change without Subversion recompiling,
> we're just as horked as we were before. -- justin
If the ABI changes without the soname changing, the downstream library
has screwed up. (Non-default configure options which affect the ABI
aren't really an issue here; if the packager or site administrator uses
such options inconsistently, then that's their problem.) APR hasn't
screwed up here, because the major version and soname changed when the
ABI changed.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 11 01:19:59 2006