From: Phil Blundell <philb@gnu.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] opkg-native: remove spurious dependency on curl-native
Date: Mon, 01 Oct 2012 16:52:07 +0100 [thread overview]
Message-ID: <1349106729.32611.61.camel@phil-desktop> (raw)
All variants of opkg are currently configured --disable-curl so there
seems no point in depending on it.
Signed-off-by: Phil Blundell <philb@gnu.org>
---
meta/recipes-devtools/opkg/opkg.inc | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/recipes-devtools/opkg/opkg.inc b/meta/recipes-devtools/opkg/opkg.inc
index 10cd9d8..28cc6a6 100644
--- a/meta/recipes-devtools/opkg/opkg.inc
+++ b/meta/recipes-devtools/opkg/opkg.inc
@@ -7,8 +7,6 @@ BUGTRACKER = "http://code.google.com/p/opkg/issues/list"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
file://src/opkg-cl.c;beginline=1;endline=20;md5=321f658c3f6b6c832e25c8850b5dffba"
-DEPENDS_virtclass-native = "curl-native"
-DEPENDS_virtclass-nativesdk = "nativesdk-curl"
PE = "1"
INC_PR = "r10"
--
1.7.10.4
next reply other threads:[~2012-10-01 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 15:52 Phil Blundell [this message]
2012-10-02 11:04 ` [PATCH] opkg-native: remove spurious dependency on curl-native Richard Purdie
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=1349106729.32611.61.camel@phil-desktop \
--to=philb@gnu.org \
--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