On 08/25/2016 07:39 AM, Ralf Corsepius wrote:
On 08/25/2016 02:28 PM, Dominik 'Rathann' Mierzejewski
wrote:
> On Thursday, 25 August 2016 at 10:24, Ralf Corsepius wrote:
>> On 08/25/2016 10:01 AM, Nicolas Chauvet wrote:
> [...]
>>> Specially as ffmpeg doesn't do symbol version, if one process has
>>> dependencies using both version, it will crash.
>> AFAIU, as long as these packages are properly linked (and not libraries
>> not being dlopened), package deps on SONAMEs would conflict and thus
>> prevent such problems.
>
> The point is that not all SONAMEs change with each FFmpeg version bump,
> so, for example, ffmpeg-3.0.x and ffmpeg-3.1.x may have mostly the same
> SONAMEs.
This would mean these are ABI compatible.
I haven't tried to check and verify actual situation wrt. ffmpeg.
Forward, not necessarily backward (compiled with 3.1, running with 3.0). This
is where symbol versioning would help.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301
http://www.nwra.com