From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com
Subject: Re: Re: [Xen-changelog] [xen-unstable] tools: Rationalise library soname versions.
Date: Sat, 8 Dec 2007 17:17:55 +0000 [thread overview]
Message-ID: <20071208171755.GA3019@redhat.com> (raw)
In-Reply-To: <20071208014657.GA11006@totally.trollied.org.uk>
On Sat, Dec 08, 2007 at 01:46:57AM +0000, John Levon wrote:
> On Fri, Dec 07, 2007 at 04:30:09PM -0800, Xen patchbot-unstable wrote:
>
> > tools: Rationalise library soname versions.
> >
> > * Arrange for the sonames of libxenstore, libxc, libfsimage and
> > libblktap to be set from a single place in Config.mk.
>
> Grumble... I don't like this at all. You just bumped libfsimage for no
> reason. Can we please fix libfsimage back to the correct versioning?
> (that is 1.0.0)
Likewise xenstore has just been bumped for no reason. The total diff
of the public xenstore head between current 3.1.x releases and unstable
is just
$ diff -u xen-3.1.0-testing.hg/tools/xenstore/xs.h xen-unstable.hg/tools/xenstore/xs.h
--- xen-3.1.0-testing.hg/tools/xenstore/xs.h 2007-04-23 19:19:32.000000000 -0400
+++ xen-unstable.hg/tools/xenstore/xs.h 2007-10-01 12:03:55.000000000 -0400
@@ -112,7 +112,6 @@
/* Start a transaction: changes by others will not be seen during this
* transaction, and changes will not be visible to others until end.
- * You can only have one transaction at any time.
* Returns NULL on failure.
*/
xs_transaction_t xs_transaction_start(struct xs_handle *h);
This is not ABI incompatible and thus libxenstore should *not* have its
soname changed.
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.
Please revert this change and only adjust the soname of libraries which
have actually changed since the previous 3.1.2 release, which AFAICT
is only libxc.
Regards,
Dan
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-12-08 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200712080030.lB80UAdN016166@xenbits.xensource.com>
2007-12-08 1:46 ` [Xen-changelog] [xen-unstable] tools: Rationalise library soname versions John Levon
2007-12-08 17:17 ` Daniel P. Berrange [this message]
2007-12-10 9:59 ` Ian Jackson
2007-12-10 14:24 ` Daniel P. Berrange
2007-12-10 14:56 ` John Levon
2007-12-10 15:00 ` Ian Jackson
2007-12-10 15:02 ` John Levon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071208171755.GA3019@redhat.com \
--to=berrange@redhat.com \
--cc=ian.jackson@eu.citrix.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.