WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] tools: Rationalise li

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] tools: Rationalise library soname versions.
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Mon, 10 Dec 2007 14:56:51 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Delivery-date: Mon, 10 Dec 2007 06:57:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <18269.3602.133295.386977@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200712080030.lB80UAdN016166@xxxxxxxxxxxxxxxxxxxxx> <20071208014657.GA11006@xxxxxxxxxxxxxxxxxxxxxxx> <20071208171755.GA3019@xxxxxxxxxx> <18269.3602.133295.386977@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Dec 10, 2007 at 09:59:46AM +0000, Ian Jackson wrote:

> Daniel P. Berrange writes ("Re: [Xen-devel] Re: [Xen-changelog] 
> [xen-unstable] tools: Rationalise library soname versions."):
> > IMHO, the entire rationale of setting all the sonames in one place is just
> > plain wrong. Libraries evolve independantly and thus their sonames change
> > independantly. Tieing sonames to the software release version number does
> > not reflect the reality of their ABI evolution. sonames should only be
> > changed when an existing API changes in a non-backwards compatible manner
> > so its perfectly normal for an soname to stay the same across multiple
> > releases if nothing changes, or merely new APIs are added without changing
> > existing APIs.
> 
> In principle I agree with you.  However, in practice the project has
> not been able to maintain the discipline needed to bump a soname when
> the ABI changes.

Please change libfsimage back. I am watching it carefully and as the
original author I do not want or intend the ABI to change (certainly not
incompatibly).

Indeed originally I hoped that this would be packaged separately from
Xen, but it didn't work out like that alas.

Tying a generic library's interface version to Xen's non-stable, mostly
non-usable library interfaces is 100% wrong.

regards
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel