diff options
| author | Qing He <qing.he@intel.com> | 2010-07-16 12:48:08 +0800 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-07-23 23:53:29 +0100 |
| commit | 63d56523555b000a4b52027b68d0e7f33bf6a2ec (patch) | |
| tree | a3857b1b8e402a640ca5fb4ffa6e5d37d61e3f64 /meta/packages/python/python-pygtk | |
| parent | 74388f763a9213d826652f647a46b8a6be45496f (diff) | |
| download | openembedded-core-63d56523555b000a4b52027b68d0e7f33bf6a2ec.tar.gz openembedded-core-63d56523555b000a4b52027b68d0e7f33bf6a2ec.tar.bz2 openembedded-core-63d56523555b000a4b52027b68d0e7f33bf6a2ec.tar.xz openembedded-core-63d56523555b000a4b52027b68d0e7f33bf6a2ec.zip | |
libusb-compat: upgrade to version 0.1.3
from 0.0.9, also remove libusb recipe (see below)
changes:
- remove some unnecessary logics derived from libusb-0.1
- now PROVIDES libusb
- bluez4 depends on libusb instead of libusb-compat
libusb-0.1 vs. libusb-compat
libusb-compat is intended to be a drop-in replacement of libusb-0.1,
building on top of libusb-1.0 (which has different API from -0.1).
Few known packages don't work with libusb-compat, notable example
is libmtp. Since most packages work very well with libusb-compat,
and libusb-compat doesn't suffer from power consumption issue of
libusb-0.1 (which is often very important for embedded systems),
drop libusb-0.1 and move to libusb-compat completely. If we see
any problems in the future, either the package should be fixed
or we can add back libusb-0.1 as needed.
Signed-off-by: Qing He <qing.he@intel.com>
Diffstat (limited to 'meta/packages/python/python-pygtk')
0 files changed, 0 insertions, 0 deletions