BerkeleyDB 6 symbol versioning and associated problems
Joe Orton
jorton at redhat.com
Wed May 7 13:39:11 UTC 2014
On Wed, May 07, 2014 at 03:19:42PM +0200, Jan Staněk wrote:
> One of the planned parts of the F21 System Wide Change: BerkeleyDB 6 [1]
> is the introduction of downstream symbol versioning of both versions of
> the libraries (libdb with v6 and libdb5 with v5). This part is planned
> in order to not introduce bugs similar to [2]. However, if we introduce
> downstream versioning (as upstream is generally unresponsive), then we
> face the problem similar to [3].
If we keep libdb5 (forever?) then the [3] problem is less of an issue,
IMO. Given that portably linking against libdb has historically been a
major headache I'd be surprised if there are any binary third-party apps
which even try doing this, to be honest.
I don't claim to understand the licensing matrix here, though, is there
any background reading on that? Can we even switch *anything* which is
potentially linked into httpd to using BDB 6? If not then basically
nothing in $libdir can link against BDB 6.
Regards, Joe
More information about the devel
mailing list