From: Phil Blundell <pb@pbcl.net>
To: Saul Wold <sgw@linux.intel.com>
Cc: Yevhen Kyriukha <kirgene@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] curl: build with c-ares library support.
Date: Tue, 12 Nov 2013 23:53:08 +0000 [thread overview]
Message-ID: <1384300388.3828.36.camel@x121e.pbcl.net> (raw)
In-Reply-To: <5282AEB6.3060706@linux.intel.com>
On Tue, 2013-11-12 at 14:41 -0800, Saul Wold wrote:
> Additionally, if adding this to oe-core, it needs to be in it's own
> patch crediting the orignal author / layer, I found a 1.10 version in
> the meta-webos-ports, is this where it came from?
There is a c-ares recipe in oe-classic which looks quite similar to this
one and I suspect that's probably where it came from (though perhaps
indirectly).
But, configuring curl to use c-ares support is not as trivial a change
as it might appear and there is a significant chance that it will cause
unforeseen (and probably unwanted) effects for at least some people.
Adding a PACKAGECONFIG option for it which defaults to off would
obviously be fine, and changing the default to be the libcurl internal
threaded resolver (which would probably fix the original complaint as
well, and doesn't require any extra recipes) might also be fine, but
enabling c-ares by default is not something that should be done
capriciously.
p.
next prev parent reply other threads:[~2013-11-12 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 23:42 [PATCH] curl: build with c-ares library support Yevhen Kyriukha
2013-11-12 22:41 ` Saul Wold
2013-11-12 23:53 ` Phil Blundell [this message]
2013-11-12 23:36 ` Saul Wold
2013-11-13 11:35 ` Phil Blundell
-- strict thread matches above, loose matches on Subject: below --
2013-11-13 0:56 Yevhen Kyriukha
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=1384300388.3828.36.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=kirgene@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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