[Pkg-xen-devel] Changes for 3.2

Ian Jackson Ian.Jackson at eu.citrix.com
Mon Dec 10 14:22:10 UTC 2007


Bastian Blank writes ("Re: [Pkg-xen-devel] Changes for 3.2"):
> On Mon, Dec 10, 2007 at 11:47:05AM +0000, Ian Jackson wrote:
> > I see.  Well, no, I don't quite see.  Why is there a problem with a
> > multi-component soname version ?
> 
> For example you won't be able to change it if necessary for example for
> a security fix. Several of this libs a security sensitive and sometimes
> it is necessary to change the API/ABI to fix problems.

Oh, I see.  Yes, the soname version shouldn't be mechanically tied to
the distribution version - after my change it still isn't.  It's just
that I'm adopting the convention of using the release version number
as the soname version, because as you observed, at Xen upstream we've
not been good at flagging ABI changes and incrementing the version
number.

For patch releases, security releases, etc., we would increment the
minor number anyway, not the soname version.  I would try hard to
avoid introducing ABI breakages in security fixes.

> > I think it might be helpful if you participated in the relevant thread
> > on xen-devel.
> 
> Will take a look into it later.

Thanks.

Ian.



More information about the Pkg-xen-devel mailing list