Re: Bug#367853: libdb transition policy?
On 30 May 2006, at 12:50, Gerfried Fuchs wrote:
Sorry for late response.
* "Nikita V. Youshchenko" <firstname.lastname@example.org> [2006-05-24 12:10]:
However, contrary to what the NM templates suggest, symbol
is not a cure-all for all ABI incompatibilities. If libetpan
a DB_ENV * in its API, you need to port all its dependencies
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
version of libetpan (without soname change or package name change)
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
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.
In fact, I checked the code and it does not this, the database won't
be regenerated but that might be a enhancement to implement in
libetpan. Do we need a release to fix this ?
That means that cache files must be deleted by the user.
DINH Viêt Hoà