> On Feb 9, 2016, at 11:41 AM, Nicolas Dechesne <nicolas.deche...@linaro.org> > wrote: > > On Tue, Feb 9, 2016 at 8:04 PM, Khem Raj <raj.k...@gmail.com> wrote: >> Think of crypto policy point of view > > why not. this is probably a good thing. But I don't think we should > block the current patches as they are. If we want to add a > DISTRO_FEATURES the patches we did in mesa and xserver are needed > anyways. Once every possible 'crypto' config are available as > PACKAGECONFIG we simply need to add one line to pick the one we need > based on DISTRO_FEATURE content. So I think we should merge them, and > discuss/plan how to add crypto as a distro policy.
Thats ok. However, if there is a time to do something to consolidate crypto backend policy then such instances are the right one. I know you have a solution for your problem.
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
