On Thu, Sep 18, 2008 at 02:07:19PM -0700, Dan Kegel wrote: > On Thu, Sep 18, 2008 at 2:03 PM, Julien Cristau <[EMAIL PROTECTED]> wrote: > >> Going forward, though, can you avoid potential issues like this > >> by maintaining better ABI compatibility between versions? > >> i.e. when you add a libncurses.so.7, can you make it so > >> that all apps that linked against libncurses.so.6 still continue > >> to work without recompilation?
> > This doesn't make any sense. If all apps linked against the previous > > version continued to work without recompilation, it wouldn't be an > > incompatible ABI change, and so wouldn't require a SONAME bump. > You still need an SONAME burp if some apps linked against the > newer library (say, those using new features) would fail with the older one. > i.e. unless a change is both forward and backwards compatible, > you can't get away without some sort of burp. (Or am I confused?) This is not how SONAMEs are used, no. SONAMEs are changed when an application built against the old version of the library can't be used with the new version of the library. When the converse is true, that a new version of the application can't be used with the old version of the library, that's signaled by other means (shlibs, components of the library filename that aren't represented in the SONAME, versioned symbols, etc). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
