On Thu, 5 May 2011 10:19, Stefan Seyfried
On Thu, 05 May 2011 01:13:32 +0200 Dave Plater
wrote: On 05/04/2011 10:52 PM, Stefan Seyfried wrote:
bluez-4.93 got hid2hci back, it was on holiday in the udev sources for some time.
Unfortunately, the test build fails:
+ /usr/lib/rpm/brp-rpath + /usr/lib/rpm/brp-pie + /usr/lib/rpm/brp-rootfs library /lib/udev/hid2hci is linked against libraries in /usr or /opt libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f77e36e7000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f77e2f5d000)
Stupid (or maybe inteligent) question, what happens if you reverse the situation in %install and have the target in in the directory where the link is and the link in the targets original directory? <snip>
What I don't really get is: why is libusb-1_0-0 / libusb-0_1-4 in /usr/{lib,lib64}/ and not in /{lib,lib64}/ ? Isn't it defined the way that libs for boot should be in /{lib,lib64}/ ? the way bluez uses libusb, and also some lan/wlan/storage-over-usb, software, I can't find a point for libusb to reside in /usr/. Is there some consens / thought / definition why libusb is in /usr/ beyond inerta / original-non-boot-usage ? I'm asking because I can't find any docu why it is this way. Regards, Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org