Hi!
Sorry for late response.
* "Nikita V. Youshchenko" <yoush@cs.msu.su> [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 dependencies
to the
new Berkeley DB version.
No, libetpan uses libdb only internally, and does not export it.
So I guess the question is to people who maintain etpan-ng and
sylpheed-claws-gtk2 - is it safe for your packages if I will
upload new
version of libetpan (without soname change or package name change)
that
will link against libdb4.4?
I don't know if anyone has tried to, but I spoke to Hoa (= upstream)
about the thing, and it was like I expected: libetpan uses libdb
for its
cache files. If it can't read them (like, b0rked file, or incompatible
old db file) it would get regenerated anyway. So there is no
compatibility problem with changing the libdb in libetpan at all.