mechanism to retain system library versions

[Miloslav Trmač]

On Wed, Dec 18, 2013 at 2:55 PM, Stanislav Ochotnicky
<sochotnicky at redhat.com> wrote:
> Quoting Neal Becker (2013-12-18 14:06:23)
>> During the past few months, I've switched from building my software against a
>> bundled version of boost libraries, to building against the system boost libs.
>>
>> On updating to f20, all of my software became broken, because the library
>> versions it was linked with were removed.
>>
>> So I had to race to rebuild all my software, and hope nothing broke when
>> rebuilt.
>>
>> I think this situation is unfortunate.  We do have library versioning, so
>> different versions could coexist.
>>
>> How do others solve this problem, or can anyone think of a solution?
>
> So what would you have us (Fedora maintainers) do? Keep a separate version of
> library for each API version?
For C++, ideally persuade upstream to keep the same soname and use
symbol versioning to keep binary compatibility.  (Last time I looked,
symbol versioning with C++ was possible but really painful.)
    Mirek