Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libusb: disable on avr32
Date: Sat, 17 Nov 2012 21:13:15 +0100	[thread overview]
Message-ID: <87sj88rns4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAHt8ZCMF-cvx4W+GrGUxqn1iBx9XDmGutVv-xGr1uF4M=o-A1A@mail.gmail.com> (Simon Dawson's message of "Sat, 17 Nov 2012 20:02:55 +0000")

>>>>> "Simon" == Simon Dawson <spdawson@gmail.com> writes:

 Simon> Hi Peter; thanks for the feedback.
 Simon> On 17 November 2012 19:58, Peter Korsgaard <jacmet@uclibc.org> wrote:
 >> What about libusb's reverse dependencies?
 >> 
 >> git grep 'select BR2_PACKAGE_LIBUSB'
 >> package/bluez_utils/Config.in:  select BR2_PACKAGE_LIBUSB
 >> package/ccid/Config.in: select BR2_PACKAGE_LIBUSB
 >> package/libftdi/Config.in:      select BR2_PACKAGE_LIBUSB
 >> package/libftdi/Config.in:      select BR2_PACKAGE_LIBUSB_COMPAT
 >> package/libhid/Config.in:       select BR2_PACKAGE_LIBUSB
 >> package/libhid/Config.in:       select BR2_PACKAGE_LIBUSB_COMPAT
 >> package/libiqrf/Config.in:      select BR2_PACKAGE_LIBUSB
 >> package/libnfc/Config.in:       select BR2_PACKAGE_LIBUSB
 >> package/libnfc/Config.in:       select BR2_PACKAGE_LIBUSB_COMPAT
 >> package/openocd/Config.in:      select BR2_PACKAGE_LIBUSB
 >> package/openocd/Config.in:      select BR2_PACKAGE_LIBUSB_COMPAT
 >> package/pcsc-lite/Config.in:    select BR2_PACKAGE_LIBUSB
 >> package/python-nfc/Config.in:   select BR2_PACKAGE_LIBUSB
 >> package/python-nfc/Config.in:   select BR2_PACKAGE_LIBUSB_COMPAT
 >> package/usb_modeswitch/Config.in:       select BR2_PACKAGE_LIBUSB
 >> package/usb_modeswitch/Config.in:       select BR2_PACKAGE_LIBUSB_COMPAT
 >> package/usbutils/Config.in:     select BR2_PACKAGE_LIBUSB

 Simon> Ah, yes. What's the right thing to do here? I don't really like the
 Simon> thought of that "depends on !BR2_avr32" all over the place, but I
 Simon> guess that's the cleanest solution, right?

Yes, that's the only solution we have right now.

Remember to look recursively upwards. These libusb users might be
selected by other packages.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-11-17 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 19:55 [Buildroot] [PATCH] libusb: disable on avr32 spdawson at gmail.com
2012-11-17 19:58 ` Peter Korsgaard
2012-11-17 20:02   ` Simon Dawson
2012-11-17 20:13     ` Peter Korsgaard [this message]
2012-11-17 20:19       ` Simon Dawson

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=87sj88rns4.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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