From: Scott James Remnant <scott@ubuntu.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org, util-linux-ng@vger.kernel.org
Subject: Re: [PATCH] debian: Remove uuid packages
Date: Sun, 19 Jul 2009 15:56:24 +0100 [thread overview]
Message-ID: <1248015384.4524.23.camel@quest> (raw)
In-Reply-To: <20090719011329.GC2416@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Sat, 2009-07-18 at 21:13 -0400, Theodore Tso wrote:
> On Fri, Jul 17, 2009 at 02:48:51AM -0400, Andreas Dilger wrote:
> > On Jul 16, 2009 19:59 +0100, Scott James Remnant wrote:
> > > +Build-Depends: texi2html (>= 1.76), gettext, texinfo, dc, pkg-config, dietlibc-dev (>> 0.30) [alpha amd64 arm hppa i386 ia64 mips mipsel powerpc ppc64 s390 sparc], debhelper (>= 7.0), libblkid-dev (>= 2.16), libuuid-dev (>= 2.16)
> >
> > Same question as for libblkid-dev... Ideally, even thought the package
> > version is 2.x, the ABI hasn't changed (AFAIK, that was a hard requirement)
> > so this should really still be called libuuid1 for compatibility.
>
> The so version number for the package is still 1; so the packages
> containing the binary shared libraries are libuuid1 and libblkid1.
> What gets confusing is that version numbers for libblkid-dev,
> libuuid-dev, libblkid1, and libuuid1 will be 2.16.x, not because of
> any soversion number, but because that's the version number of
> util-linux-ng.
>
It's always dangerous to start confusing SONAMEs or version numbers, and
doubly so to attempt to make them match.
The SONAME of a library reflects its ABI, the version number of software
reflects the author's opinions about it.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-07-19 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 18:59 [PATCH] debian: Remove uuid packages Scott James Remnant
[not found] ` <E1MRWBq-0000yy-0F-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
2009-07-17 6:48 ` Andreas Dilger
[not found] ` <20090717064851.GJ4207-RIaA196FMs1uuQVovAj/GogTZbYi8/ss@public.gmane.org>
2009-07-19 1:13 ` Theodore Tso
2009-07-19 14:56 ` Scott James Remnant [this message]
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=1248015384.4524.23.camel@quest \
--to=scott@ubuntu.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--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).