Re: [PATCH] curl: build with c-ares library support.

[Saul Wold <sgw@linux.intel.com>]

On 11/12/2013 03:53 PM, Phil Blundell wrote:
> 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.
>
This is why I wanted to understand the orignal failure, so using 
PACKAGECONFIG sounds reasonable, I think we have had a case in the past 
where we even allowed for a non-default PACKAGECONFIG point outside of 
oe-core (I can't remember which one it was now).

Sau!

> p.
>
>
>
>