Re: rpm handling of new library symbols

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



W dniu 05.01.2013 18:37, Miloslav Trmač pisze:
> On Sat, Jan 5, 2013 at 11:38 AM, Julian Sikorski <belegdol@xxxxxxxxx> wrote:
>> a bug was recently filed against gnumeric [1], in which the program refused
>> to run due to user not having updated his whole package set and a symbol
>> being missing in the older libgsf he had installed.
>> How are such issues supposed to be handled? Surely, manually introducing a
>> versioned dependency for every library is going to be painful. Given that
>> soname bump is required only for symbols removal/change, is it that if
>> someone cherry-picks updates, then he/she keeps all the pieces in case
>> something breaks? Thank you for the input in advance.
> This is handled automatically for shared libraries that use ELF symbol
> versioning and introduce the new symbols in a new version: the
> automatically-generated provides/requires include the ELF symbol
> version.
> 
> If the library does not use symbol versioning, manually adding a
> versioned dependency is all that's left I'm afraid.
>     Mirek
> 
Is that the same as bumping soname whenever new symbols are introduced?
How is gstreamer handling this? They managed to keep stable ABI but
there were new symbols introduced at some point for sure.

Julian
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux