dev-libs/libusb:0 should not be required after emerging libusb-1 and libusb-compat packages. Reproducible: Always Steps to Reproduce: emerge -pv gok Actual Results: tries to emerge libusb:0 as dependency. Expected Results: should be okay with libusb:1 and libusb-compat. version specific dependency on libusb can be removed.
hirakendu: can you confirm that libusb-1+libusb-compat works with the hardware (actually testing it ideally)?
It emerges fine. And then I tested on my notebook with a USB mouse. Works fine. I didn't test it with anything else. To put it straight, I didn't see any difference in functionality between libusb:0 and libusb:1. So while I didn't test rigorously, it is fine I guess. Aside, frankly I was just looking for an on-screen keyboard - just for sometimes typing in other languages. And it seems that the ubuntu(?) package onboard (along with virtkey) is more suitable for this. It would be nice to add them in portage too. This bug for ebuild should be considered - http://bugs.gentoo.org/166876 .
hirakendu: Thanks for testing. I've marked it for the new virtual now. with respect to onboard/virtkey, file some package request bugs for them, some of the embedded crowd might pick them up for you (think OpenMoko).
Thanks for updating the ebuilds. Making it depend on virtual is better :). For onboard and virtkey, I thought the bug # 166876 I mentioned was about the request. I'll file a request sometime (along with ebuilds that work).
whoops, i need my coffee to work better, I missed the bug reference.
