1 |
On Mon, Feb 11, 2013 at 5:17 PM, Peter Stuge <peter@×××××.se> wrote: |
2 |
>> net-libs/libpcap-1.3.0-r1 (canusb ? virtual/libusb) |
3 |
> |
4 |
> This one has no slotted dependency. Does that matter? In any case it |
5 |
> doesn't seem completely correct, since the two APIs are not |
6 |
> compatible. |
7 |
|
8 |
It doesn't matter in this case, because canusb is disabled anyway. The |
9 |
real dependencies are: |
10 |
|
11 |
app-crypt/ccid-1.4.8 (usb ? virtual/libusb:1) |
12 |
dev-libs/libusb-compat-0.1.4 (virtual/libusb:1) |
13 |
dev-libs/openobex-1.5 (usb ? virtual/libusb:0) |
14 |
media-libs/libmtp-1.1.5 (virtual/libusb:1) |
15 |
net-wireless/bluez-4.101-r5 (usb ? virtual/libusb:0) |
16 |
sys-apps/usb_modeswitch-1.2.5_p20121109 (virtual/libusb:0) |
17 |
sys-apps/usbutils-006 (virtual/libusb:1) |
18 |
virtual/libusb-0 (>=dev-libs/libusb-0.1.12-r7:0) |
19 |
virtual/libusb-1 (>=dev-libs/libusb-1.0.9:1) |
20 |
|
21 |
>> Any idea on what's going on? BFS instead of DFS search when |
22 |
>> satisfying "||"? |
23 |
> |
24 |
> Seems a good explanation.. Can you try swapping the two in the virtual? |
25 |
|
26 |
BFS and DFS both work left-to-right, but in absence of both |
27 |
dev-libs/libusb:0 or :1, the path via libusb-compat to |
28 |
dev-libs/libusb:1 is longer than the immediate path to |
29 |
dev-libs/libusb:0. I think libusb-compat was selected correctly |
30 |
previously (a few months ago), so perhaps and update in portage caused |
31 |
the issue. On the other hand, this is just a hypothesis. |
32 |
|
33 |
-- |
34 |
Maxim Kammerer |
35 |
Liberté Linux: http://dee.su/liberte |