From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libpcap: weaken bluez-libs dependency
Date: Wed, 15 Apr 2009 10:24:23 +0100 [thread overview]
Message-ID: <49E5A7C7.6010809@xora.org.uk> (raw)
In-Reply-To: <1239784615-19928-1-git-send-email-khimov@altell.ru>
On 04/15/2009 09:36 AM, Roman I Khimov wrote:
> libpcap can be used in distros where no bluetooth support will ever
> exist. So this dependency should be weakened to only exist in distros
> that explicitly need bluetooth.
> ---
> recipes/libpcap/libpcap.inc | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/libpcap/libpcap.inc b/recipes/libpcap/libpcap.inc
> index 4468a4b..81bf826 100644
> --- a/recipes/libpcap/libpcap.inc
> +++ b/recipes/libpcap/libpcap.inc
> @@ -2,7 +2,11 @@ DESCRIPTION = "Network Packet Capture Library"
> HOMEPAGE = "http://www.tcpdump.org/"
> SECTION = "libs/network"
> LICENSE = "BSD"
> -DEPENDS = "bluez-libs flex-native bison-native"
> +DEPENDS = " \
> + ${@base_contains("COMBINED_FEATURES", "bluetooth", "bluez-libs", "", d)} \
> + flex-native \
> + bison-native \
> + "
>
> PR = "r1"
>
>
NACK, this doesnt do what you think it does as you don't disable
bluetooth via any form of alteration to the build system. You have
created randomness in your build now.
Graeme
next prev parent reply other threads:[~2009-04-15 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 8:36 [PATCH] libpcap: weaken bluez-libs dependency Roman I Khimov
2009-04-15 9:04 ` Koen Kooi
2009-04-15 9:47 ` Roman I Khimov
2009-04-15 10:08 ` Andrea Adami
2009-04-15 10:47 ` Holger Schurig
2009-04-15 11:06 ` Koen Kooi
2009-04-15 9:24 ` Graeme Gregory [this message]
2009-04-15 9:41 ` Roman I Khimov
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=49E5A7C7.6010809@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.