As you can see from the conversation quoted below, apparently it is wrong
the current csound practice of installing shared libraries without
SOVERSION[1] in /usr/lib (note plugins don't need this since they are not
on /usr/lib and they are used only by csound).
I'm not sure how to fix this, since these libraries without the SOVERSION
are the language interfaces. The SOVERSION is used to indicate binary
compatibility between releases. However I don't know how SWIG-generated
interfaces maintain ABI compatibility: is there such a guarantee somewhere? 

Plus, I talked to the lua debian maintainers, and apparently you do need to
have a SOVERSION even for interface libraries. 

Anyone any ideas on how to proceed?

----

Steve Langasek wrote:

> On Fri, Aug 17, 2007 at 11:21:35AM -0400, Felipe Sateler wrote:
> 
>> > It's not a question of being able to parse the file, it's that
>> > "libcsnd.so"
>> > is not a proper name for a shared library.  dpkg-shlibdeps is warning
>> > you about what appears to be a genuine bug in one of the libraries your
>> > package depends on.
> 
>> Hm, so I have to introduce a SONAME? I will have to talk with upstream.
> 
> Yes, if you're going to ship a shared library in your package, it needs to
> have a versioned soname.



[1] SOVERSION is the major version part of a *nix library: in
libcsnd.so.X.Y, the SOVERSION would be X.
-- 

  Felipe Sateler


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net