Felipe Sateler <fsate...@gmail.com> writes: > But this will cause trouble anyway. Imagine this case: glib changes > SONAME, both app and library depend on glib. app is recompiled, gtk > isn't yet.So then app NEEDED libglib-2.0.so.1, gtk NEEDED > libglib-2.0.so.0. Kaboom!
That's what symbol versioning is for, in the general case. Provided that each library provides its own functions for accessing its own objects and doesn't let you look under the hood into objects that are directly based on underlying library ABIs, this normally works. The specific case of gtk and glib is incestuous in ways that makes it hard to come up with a robust solution. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
