From: Karel Zak <kzak@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Scott James Remnant <scott@ubuntu.com>,
linux-ext4@vger.kernel.org, util-linux-ng@vger.kernel.org
Subject: Re: [PATCH] configure: Disable libblkid by default
Date: Sun, 19 Jul 2009 23:27:14 +0200 [thread overview]
Message-ID: <20090719212714.GA6886@nb.net.home> (raw)
In-Reply-To: <20090719115617.GF2416@mit.edu>
Hi Ted,
On Sun, Jul 19, 2009 at 07:56:17AM -0400, Theodore Tso wrote:
> Also, apparently no once noticed until now, but there's a bug in the
> util-linux-ng's uuid.sym file. The uuid_pack and uuid_unpack symbols
> are missing, because someone forgot to include them in the uuid.sym
> file.
is it really bug? Why do you want to export symbols that are not part
of the library API?
I don't see uuid_pack and uuid_unpack in uuid.h. I guess nobody use
these symbols ;-)
> BTW, **why** is util-linux-ng gratuitously introducing backwards
> incompatibility such that packages built with util-linux-ng won't work
> with the older shared libraries? There's no reason to do this.
Good point. I agree that (at first glance) there's no reason for this
change. But...
"If possible, projects implementing generally usable DSOs
should use symbol versioning from day one."
-- How To Write Shared Libraries, Ulrich Drepper
I agree with Ulrich, symbol versioning is really really good thing.
Unfortunately, it's not possible to combine versioned symbols with
anonymous (without version) symbols. It means after first change to
the library ABI we will need to introduce UUID_1.0 for old symbols.
The move from e2fsprogs to util-linux-ng is excellent opportunity
to introduce ABI versioning to libuuid. I don't think this change has
negative impact to our distributions in practice.
How often people need to mix old libuuid (from e2fsprogs) with
applications compiled against new libuuid (from util-linux-ng)? I
guess almost never...
> Argh, util-linux-ng 2.16 has already been released; is it too late to
> undo this change?
I think yes, it's too late.
A new version (2.16.1) without UUID_1.0 will require mass rebuild in
all distributions/systems where are libuuid applications with ABI
versioning. IMHO this is much more painful that impossibility to
downgrade to the old libuuid (from e2fsprogs).
Maybe we can add --disable-{libuuid,libblkid}-versioning for people
who need to bypass the default behaviour.
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2009-07-19 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 18:46 [PATCH] configure: Disable libblkid by default Scott James Remnant
[not found] ` <E1MRWBp-0000yN-9a-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
2009-07-17 14:36 ` Theodore Tso
[not found] ` <20090717143637.GM8508-3s7WtUTddSA@public.gmane.org>
2009-07-17 14:54 ` Scott James Remnant
2009-07-17 15:02 ` Theodore Tso
2009-07-17 15:14 ` Scott James Remnant
2009-07-19 11:56 ` Theodore Tso
2009-07-19 14:59 ` Scott James Remnant
2009-07-19 21:27 ` Karel Zak [this message]
[not found] ` <20090719212714.GA6886-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2009-07-20 14:23 ` Theodore Tso
2009-07-20 14:26 ` Christoph Hellwig
[not found] ` <20090720142337.GH2416-3s7WtUTddSA@public.gmane.org>
2009-07-20 14:37 ` Scott James Remnant
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=20090719212714.GA6886@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=scott@ubuntu.com \
--cc=tytso@mit.edu \
--cc=util-linux-ng@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).