From: Maxim Kammerer <mk@dee.su>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libusb-compat preference in virtual/libusb:0 not strong enough?
Date: Mon, 11 Feb 2013 17:42:21 +0200 [thread overview]
Message-ID: <CAHsXYDCfhuGOCsOquXXtGhtXTQvVOUkwju27HQOvwUdfQc4o9A@mail.gmail.com> (raw)
In-Reply-To: <20130211151728.2557.qmail@stuge.se>
On Mon, Feb 11, 2013 at 5:17 PM, Peter Stuge <peter@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.
--
Maxim Kammerer
Liberté Linux: http://dee.su/liberte
next prev parent reply other threads:[~2013-02-11 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:18 [gentoo-dev] libusb-compat preference in virtual/libusb:0 not strong enough? Maxim Kammerer
2013-02-11 15:17 ` Peter Stuge
2013-02-11 15:21 ` Diego Elio Pettenò
2013-02-11 16:44 ` Peter Stuge
2013-02-11 16:47 ` Diego Elio Pettenò
2013-02-11 16:54 ` Peter Stuge
2013-02-11 17:01 ` Diego Elio Pettenò
2013-02-11 17:09 ` Zac Medico
2013-02-11 17:22 ` Peter Stuge
2013-02-11 18:05 ` Maxim Kammerer
2013-02-12 0:37 ` Maxim Kammerer
2013-02-11 15:42 ` Maxim Kammerer [this message]
2013-02-11 15:47 ` Zac Medico
2013-02-11 15:40 ` Zac Medico
2013-02-11 16:04 ` Maxim Kammerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHsXYDCfhuGOCsOquXXtGhtXTQvVOUkwju27HQOvwUdfQc4o9A@mail.gmail.com \
--to=mk@dee.su \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox