[OE-core] [PATCH 4/4] xserver-xorg: Add PACKAGECONFIG for crypto libraries

Mark Hatle mark.hatle at windriver.com
Tue Feb 9 18:04:05 UTC 2016


On 2/9/16 11:54 AM, Khem Raj wrote:
> 
>> On Feb 9, 2016, at 1:39 AM, Nicolas Dechesne <nicolas.dechesne at linaro.org> wrote:
>>
>> On Tue, Feb 9, 2016 at 10:24 AM, Jussi Kukkonen
>> <jussi.kukkonen at intel.com> wrote:
>>> Default to libcrypto (openssl) as before.
>>>
>>> Signed-off-by: Jussi Kukkonen <jussi.kukkonen at intel.com>
>>
>> Looks good to me. this is the same implementation I used in the mesa
>> patch.. so we need to make sure that any review feedback is applied to
>> both before merging the too,
> 
> since its spans multiple recipes would it be better to control it with
> a global knob instead of packageconfig.

I'm not sure it makes sense in -this- case..  but I've more then once thought
that it would be nice for a global distro "this is the preferred crypto engine"
setting.

That way you could do things like default to openssl, libgcrypt, libnss, etc..
whatever is appropriate for the system you are building.  It wouldn't promise
that everything would just use that crypto backend, but things that could -- should.

(This is certainly a more extensive patch then what's being discussed here..)

--Mark

>> should we get any review feedback.. but
>> in any case:
>>
>> Reviewed-by: Nicolas Dechesne <nicolas.dechesne at linaro.org>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 
> 




More information about the Openembedded-core mailing list