Bug#427166: jed: compiled against S-Lang 20007 but linked to 20006

[Rafael Laboissiere]

* John E. Davis <davis at space.mit.edu> [2007-06-03 16:57]:

> On Sun, 3 Jun 2007 21:00:01 +0200, Rafael Laboissiere <rafael at debian.org> said:
> >In order to circumvent this problem, we could force jed in Debian to depend
> >on libslang2 (>= 2.0.7).  For now, the jed package depends on libslang2 (>=
> 
> It seems to me that if jed was compiled against 2.0.7, then the depend
> ought to be >= 2.0.7.

Well, if 2.0.7 is backward compatible with 2.0.6 (which has to be the case
because there was no bump in the soname between the two versions), then the
depends can be >= 2.0.6.

> Also in addition to bug fixes, newer versions generally include new
> intrinsics and new functionality.  While I maintain backward
> compatibility and make no claims about forward compatibility.  For
> example, slang-2.0.7 added several SLfile_*_method functions to the
> API.

Oh, if there was additions in the API between 2.0.6 and 2.07, then you are
not following the common rules for given soversions for the library.  In
libslang 2.0.6, we had:

    /lib/libslang.so.2.0.6

In libslang 2.0.7, we should have:

    /lib/libslang.so.2.1.0

It seems that you are equating the source version to the soversion.  This is
not the Right Thing (TM) to do.  For instance, see "info libtool":

    6.3 Updating library version information
    ========================================
   [snip] 
   *_Never_* try to set the interface numbers so that they correspond
   to the release number of your package.  This is an abuse that only
   fosters misunderstanding of the purpose of library versions.
   
-- 
Rafael