For applications that explicitly load libusb.so at runtime with a dlopen
call.
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.
Yeah, that's a fair point. Though I would argue that keep changing the ABI
isn't a great idea, and if they didn't then problems like this wouldn't
arise (but I know that's an upstream issue, not the fault of your package).
Richard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
