On Tue, Mar 01, 2016 at 03:05:10PM +0000, Rainer Weikusat wrote:
>
> But this already exists. Eg, the machine I usually use for development
> (Debian 6 based) has the following version of libdb installed:
>
> ii libdb4.2 4.2.52+dfsg-5 Berkeley v4.2 Database Libraries [runtime]
> ii libdb4.5 4.5.20-13 Berkeley v4.5 Database Libraries [runtime]
> ii libdb4.6 4.6.21-16 Berkeley v4.6 Database Libraries [runtime]
> ii libdb4.7 4.7.25-9 Berkeley v4.7 Database Libraries [runtime]
> ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [runtime]
> ii libdb4.8-dev 4.8.30-2 Berkeley v4.8 Database Libraries [development]
>
> That's just a matter of using a different soname whenever something
> changes in a backward incompatible way. Even for cases where the soname
> is fixed 'for political reasons' aka 'glibc', the issue is supposed to
> be handled transparently via symbol versioning.
It seems to me that a decade or more ago, I read that this was the standard
Linux way to name multiple versions of libraries.
-- hendrik
::
Re: [DNG] leveldb support proposal
