On 02/11/2013 07:42 AM, Maxim Kammerer wrote: > On Mon, Feb 11, 2013 at 5:17 PM, Peter Stuge <pe...@stuge.se> wrote: >>> net-libs/libpcap-1.3.0-r1 (canusb ? virtual/libusb) >> >> This one has no slotted dependency. Does that matter? In any case it >> doesn't seem completely correct, since the two APIs are not >> compatible. > > It doesn't matter in this case, because canusb is disabled anyway. The > real dependencies are: > > app-crypt/ccid-1.4.8 (usb ? virtual/libusb:1) > dev-libs/libusb-compat-0.1.4 (virtual/libusb:1) > dev-libs/openobex-1.5 (usb ? virtual/libusb:0) > media-libs/libmtp-1.1.5 (virtual/libusb:1) > net-wireless/bluez-4.101-r5 (usb ? virtual/libusb:0) > sys-apps/usb_modeswitch-1.2.5_p20121109 (virtual/libusb:0) > sys-apps/usbutils-006 (virtual/libusb:1) > virtual/libusb-0 (>=dev-libs/libusb-0.1.12-r7:0) > virtual/libusb-1 (>=dev-libs/libusb-1.0.9:1) > >>> Any idea on what's going on? BFS instead of DFS search when >>> satisfying "||"? >> >> Seems a good explanation.. Can you try swapping the two in the virtual? > > BFS and DFS both work left-to-right, but in absence of both > dev-libs/libusb:0 or :1, the path via libusb-compat to > dev-libs/libusb:1 is longer than the immediate path to > dev-libs/libusb:0. I think libusb-compat was selected correctly > previously (a few months ago), so perhaps and update in portage caused > the issue. On the other hand, this is just a hypothesis.
There has been no change in the portage behavior. Since libusb-compat is on the left, it's supposed to be preferred. -- Thanks, Zac
