Hi!
Sorry for late response.
* Nikita V. Youshchenko [EMAIL PROTECTED] [2006-05-24 12:10]:
However, contrary to what the NM templates suggest, symbol versioning
is not a cure-all for all ABI incompatibilities. If libetpan returns
a DB_ENV * in its API, you need to port[1] all its
Have fun with updating the library, it won't affect depending packages.
:) Some times are that easy to solve, you know?
Ok, will upload today :)
pgpHAIvddyz9K.pgp
Description: PGP signature
On 30 May 2006, at 12:50, Gerfried Fuchs wrote:
Hi!
Sorry for late response.
* Nikita V. Youshchenko [EMAIL PROTECTED] [2006-05-24 12:10]:
However, contrary to what the NM templates suggest, symbol
versioning
is not a cure-all for all ABI incompatibilities. If libetpan
returns
a
On Wed, May 24, 2006 at 07:59:48AM +0200, Florian Weimer wrote:
Why that? It would only affect packages that (correctly or wrongly) also
depend on libdb4.2. (And libdb4.2 unfortunatly doesn't have versioning,
otherwise, it wouldn't be any issue; lidb4.3 and libdb4.4 are better in
that
* Andreas Barth:
Why that? It would only affect packages that (correctly or wrongly) also
depend on libdb4.2. (And libdb4.2 unfortunatly doesn't have versioning,
otherwise, it wouldn't be any issue; lidb4.3 and libdb4.4 are better in
that regard.)
Berkeley DB 4.2 was compiled such that every
* Andreas Barth:
Why that? It would only affect packages that (correctly or wrongly)
also depend on libdb4.2. (And libdb4.2 unfortunatly doesn't have
versioning, otherwise, it wouldn't be any issue; lidb4.3 and libdb4.4
are better in that regard.)
Berkeley DB 4.2 was compiled such that
* Nikita V. Youshchenko:
* Nikita V. Youshchenko:
However, if I will build library against libdb4.4 instead of
libdb4.2, this will probably break any binaries built against the
library - both packaged and local.
What kind of interface does libetpan expose? Based on the package
* Nikita V. Youshchenko:
However, if I will build library against libdb4.4 instead of
libdb4.2, this will probably break any binaries built against the
library - both packaged and local.
What kind of interface does libetpan expose? Based on the package
description, I wouldn't expect
[CCing to -devel and to people who maintain packages that depend on
libetpan]
Package: libetpan
Severity: wishlist
Hi,
currently several versions of the berkeley db libraries are used in the
archive: libdb[4.2,4.3,4.4].
Please consider upgrading to libdb4.4 in order to ship etch with
* Nikita V. Youshchenko:
However, if I will build library against libdb4.4 instead of
libdb4.2, this will probably break any binaries built against the
library - both packaged and local.
What kind of interface does libetpan expose? Based on the package
description, I wouldn't expect the
* Nikita V. Youshchenko ([EMAIL PROTECTED]) [060523 17:22]:
However, if I will build library against libdb4.4 instead of libdb4.2, this
will probably break any binaries built against the library - both packaged
and local.
Why that? It would only affect packages that (correctly or wrongly)
11 matches
Mail list logo
