From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] curl: make CURL_FEATURES configurable again
Date: Sat, 30 Oct 2010 06:15:45 -0400 [thread overview]
Message-ID: <20101030101545.GB21651@denix.org> (raw)
In-Reply-To: <4CCAE1DB.1030504@cbnco.com>
On Fri, Oct 29, 2010 at 11:01:47AM -0400, Michael Smith wrote:
> Khem Raj wrote:
>> On Thu, Oct 28, 2010 at 2:09 PM, Michael Smith <msmith@cbnco.com> wrote:
>>> Do you have any thoughts on how to solve it? There is not much point to
>>> having CURL_FEATURES as a variable if it's not configurable. I can just
>>> hack
>>> over it in an amend.inc, but the recipe as it stands is broken.
>> yes if we had the recipe type overrides for native sdk and target
>> separate then this could
>> be done probably by appending to concerning override
>
> OK, what if we get rid of CURL_FEATURES entirely, and the anon python that
> handles it. No one in-tree is using CURL_FEATURES, and it's been broken for
> a couple weeks now.
>
> It'll be easy enough to override the depends and configure opts in a recipe
> amend for anyone who needs that control (i.e. me).
It has been discussed before (check irc logs 7-10 days ago) and Khem made a
change to introduce new override called "target", which can be used in this
case. Anyway, I ended up fixing it by amend in my overlay:
http://arago-project.org/git/?p=arago.git;a=commitdiff;h=37979c41a04f7712dbf9c325871fea7c01cc737a
--
Denys
next prev parent reply other threads:[~2010-10-30 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 17:22 [PATCH] curl: make CURL_FEATURES configurable again Michael Smith
2010-10-28 18:30 ` Khem Raj
2010-10-28 18:49 ` Michael Smith
2010-10-28 20:53 ` Khem Raj
2010-10-28 21:09 ` Michael Smith
2010-10-28 22:34 ` Khem Raj
2010-10-29 15:01 ` Michael Smith
2010-10-30 10:15 ` Denys Dmytriyenko [this message]
2010-11-02 13:49 ` Michael Smith
2010-10-29 15:02 ` [PATCH v2] curl: remove anon python block Michael Smith
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=20101030101545.GB21651@denix.org \
--to=denis@denix.org \
--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.