Jason,

     Before this change, the XercesLib was named like
<name>majorversion_minorversion_revision,
namely, libxerces-c1_3_0, libxerces-c1_6_0, and libxerces-c1_6_1, which is
libxerces-c.so.1.3.0 ,
libxerces-c.so.1.6.0 and libxerces-c.so.1.6.1 in terms of Linux naming
convention. And often,
change in revision implies a bug fix release while change in the minversion
implies a **MAJOR**
release, such as new features implemented and most probably broke the ABI.

      Assuming we had built our library in this way, and all of them would've
shared the same soname,
libxerces.so.1, and that no doubtly, violated what is required that all libraries
share the same soname
shall have the identical ABI.

      To reflect the fact that minor version would change the ABI, I thought it
was appropriate to
mingle our version(s) no, and that is why we came up with libxerces-c.so.17.0
(with the soname as libxerces-c.so.17 ). Thus we shall be free to break ABI in
our next release
be it 1.8 or 2.0 or whatever.

     Buillaume, one thing for sure, the next release will not have the same
soname libxerces-c.so.17 -:)
and you need not to worry about the ABI.

Rgds,
PeiYong

"Jason E. Stewart" wrote:

> "PeiYong PY Zhang" <[EMAIL PROTECTED]> writes:
>
> > Guillaume Morin wrote:
> >
> > > Thanks a lot for implementing this. Could you confirm that you set
> > > 'libxerces-c.so.17' as soname and that means that you'll take care of
> > > not changing the ABI between minor releases ?
> > >
> > > Regards,
> > >
> >
> > Guillaume,
> >
> >     Yes, the soname is 'libxerces-c.so.17'. If next version/release gona to
> > change the ABI, we will **DEFINITELY** change the soname as well.
>
> Actually I believe that Guillaume is not just asking to change the
> soname, but to not make *any* ABI changes unless you change the MAJOR
> VERSION number. This has never happened in Xerces, the ABI changes
> every minor version change, and even in some sub_version changes, for
> example between 1.5.1 and 1.5.2.
>
> If you agree to not change the ABI, then you would have to release
> Xerces 2.0, 3.0, etc if you do.
>
> Is this a correct statement of what you were asking Guillaume?
>
> Cheers,
> jas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to