Maarten Boekhold writes ("Re: Shared library dependencies revisited"):
...
> And what about packages that depend on *one* particular version of a
> library? I know of one library which will cause trouble, namely libslang.
> This library changes every minor version update so that programs compiled
> with earlier versions will not work [...]There is no problem with this - it's not even a special case. I'm assuming that the whole library version is in the soname. Of course the library soname has to be encoded into the package name, so that different versions can coexist. Can the upstream authors not be persuaded to do better ? > [...] (I'm not into shared libs, but I think > I'm correct if I say that the ABI changes not only with .so-name > changes). Yes. Ian.
