Richard Burton a écrit :
You should not need the .so file at runtime, but only during
development. That's why the .so file is in the -dev package, as for
other libraries, and as required by the policy.
Why do you need the .so file in the library package?
For applications that explicitly load libusb.so at runtime with a dlopen
call. The example I came across was in an IBM driver for a Remote
Supervisior Adapter card. Loading the lib at runtime isn't just to get
round GPL linking issues (as I first suspected) as the driver code is
also released under the GPL.
(http://www-306.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-59454)
In that case the application is broken. Using libusb.so instead of
libusb-0.1.so.4 does not guarantee that the ABI is the right one.
libusb will (probably) soon be released with a totally new ABI. Both old
and new libraries will be installable at the same time, but if the
application uses libusb.so, it will not know which library will be loaded.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`- people.debian.org/~aurel32 | www.aurel32.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
