On Tue, Oct 28, 2014 at 10:27:18PM +0100, Samuel Thibault wrote: > Andreas Beckmann, le Mon 27 Oct 2014 00:12:14 +0100, a écrit : > > On 2014-10-26 10:07, Aurelien Jarno wrote: > > > On Sun, Oct 26, 2014 at 02:48:08AM +0200, Marco d'Itri wrote: > > >> This link does not appear to have any purpose and should be removed: > > >> > > >> /usr/lib/i386-linux-gnu/libusb-0.1.so.4 -> > > >> /lib/i386-linux-gnu/libusb-0.1.so.4 > > > > > > It has been added as part of a NMU to fix bug #706278. Adding Andreas > > > Beckmann in Cc: so he can comment on that. > > > > IIRC libusb-dev installs libusb*.so into /usr/lib/triplet while > > libusb*.so.* reside in /lib/triplet. > > But why putting libusb*.so into /usr/lib/triplet and not just > /lib/triplet?
I have never seen a development package shipping a lib*.a or lib*.so in /lib or /lib/triplet. I have just tried, it seems to work at least from the toolchain point of view, but it makes lintian unhappy: W: libusb-0.1-4: dev-pkg-without-shlib-symlink lib/x86_64-linux-gnu/libusb-0.1.so.4.4.4 usr/lib/x86_64-linux-gnu/libusb-0.1.so That said it seems compliant with the policy. I don't know if there is any other drawbacks of doing so. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
