Replacing libusb1 with libusbx |
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Hi All,
I plan to replace libusb1 with libusbx, libusx is a fork of and
a drop in replacement for libusb1.
The libusbx fork was started by various libusb-1.0 developers
(almost all of them *), because the official maintainer of libusb-1.0
refused to do any stable / tarbal releases for over 18 months and in
general was very slow with merging new developments and fixes.
Don't be fooled by the recently done libusb-1.0.9 release, that
was done by the libusb-1.0 maintainer *after* the libusbx fork
was announced and had already done 2 releases. The fact that
this release only happened after the fork went public, despite
various people including me asking for a release for ages (**)
shows that forking was necessary.
Anyways, I just included this tidbit to explain why I'm replacing
libusb1 with libusbx for Fedora-18 and later. Lets not look
backwards, but forwards towards what looks to be a bright future
with libusbx :)
A rename review request can be found here:
https://bugzilla.redhat.com/show_bug.cgi?id=823886
Reviews appreciated!
Regards,
Hans
*) Full disclosure: I'm one of the libusb developers behind the fork
**) I was originally promised a 1.0.9 release in time for inclusion
into Fedora 16 gold!
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
[Fedora Announce]
[Fedora Kernel]
[Fedora Testing]
[Fedora Legacy Announce]
[Home]
[Fedora Tools]
[Fedora PHP Devel]
[Kernel List]
[Fedora Legacy]
[Fedora Maintainers]
[Fedora Maintainers]
[Fedora Desktop]
[PAM]
[Red Hat Development]
[Big List of Linux Books]
[Gimp]
[Yosemite News]