Sam Hartman <hartmans@debian.org> wrote:
> Why does this break anyway? Shouldn't Ben's db2 versioning fixes be
> sufficient?
I'm not sure what his final approach was so I can't comment on that.
But the general problem is this:
libsasl7 is linked against libdb2. Let's consider an application that's
linked to both libsasl7 and libdb2, e.g., exim. Here comes libdb3, which
cannot be loaded in the same process as libdb2 due to name space conflicts.
If you link libsasl7 against libdb3, this will break any applications
linked against the old libsasl7 and libdb2 since it will now try to load
both db2 and db3 in the same process.
Thus you must change libsasl's soname when you link it against a new
db library. Since this requires coordination between the various Linux
distributions, it is definitely not an easy thing to do.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt