From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Larson <clarson@kergoth.com>
Cc: oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: [PATCH 01/11] libpcap: Add missing libusb dependency
Date: Thu, 24 Jan 2013 22:49:09 +0000 [thread overview]
Message-ID: <1359067749.3616.23.camel@ted> (raw)
In-Reply-To: <CABcZANmaExGvf_4Vm-+00nkk905an8atzPPR946KOsOWGpwYvw@mail.gmail.com>
On Thu, 2013-01-24 at 15:42 -0700, Chris Larson wrote:
>
> On Thu, Jan 24, 2013 at 3:14 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Thu, Jan 24, 2013 at 1:50 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Do we need libusb support in libpcap? What does this
> dependency buy us
> > and couldn't we force it off instead?
>
>
> its needed to support canusb in libpcap, I would say yes we
> should
> support it but disabling it would be ok too although all my
> builds
> were silently using libusb so I think unknowingly may be but
> we are
> already shipping with canusb support.
>
> I'd personally prefer it disabled, but I'd think at the very least it
> should be a PACKAGECONFIG entry, whether its included in the default
> value of PACKAGECONFIG itself or not.
>
Agreed, PACKAGECONFIG, default off is the way to go with this IMO too.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-24 23:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 21:07 [PATCH 00/11] recipes refreshed for uclibc and systemd update to 197 Khem Raj
2013-01-24 21:07 ` [PATCH 01/11] libpcap: Add missing libusb dependency Khem Raj
2013-01-24 21:50 ` Richard Purdie
2013-01-24 22:14 ` Khem Raj
2013-01-24 22:42 ` Chris Larson
2013-01-24 22:49 ` Richard Purdie [this message]
2013-01-25 1:00 ` Khem Raj
2013-01-25 4:30 ` Khem Raj
2013-01-24 21:07 ` [PATCH 02/11] gettext: Fix build with uclibc remove upstreamed patches Khem Raj
2013-01-24 21:07 ` [PATCH 03/11] libtirpc: Disable DES functions on uclibc Khem Raj
2013-01-24 21:07 ` [PATCH 04/11] rpcbind: Dont use nss with uclibc Khem Raj
2013-01-25 14:20 ` Richard Purdie
2013-01-25 17:22 ` Khem Raj
2013-01-24 21:07 ` [PATCH 05/11] quota: inherit gettext Khem Raj
2013-01-24 21:07 ` [PATCH 06/11] icu: Fix build on uclibc Khem Raj
2013-01-24 21:07 ` [PATCH 07/11] uclibc-git/uClibc.distro: Enable UCLIBC_HAS_REENTRANT_RPC Khem Raj
2013-01-24 21:07 ` [PATCH 08/11] tcmode-default.inc: Switch to git version of uclibc by default Khem Raj
2013-01-24 21:07 ` [PATCH 09/11] systemd: Fix build on ppc Khem Raj
2013-01-24 21:07 ` [PATCH 10/11] systemd: Upgrade to 197 Khem Raj
2013-01-25 16:04 ` Burton, Ross
2013-01-25 16:08 ` Martin Jansa
2013-01-25 16:10 ` Burton, Ross
2013-01-24 21:07 ` [PATCH 11/11] gawk: Add missing dependency on readline Khem Raj
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=1359067749.3616.23.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.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