From: Khem Raj <raj.khem@gmail.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] xserver-xorg: Add PACKAGECONFIG for crypto libraries
Date: Tue, 9 Feb 2016 13:21:58 -0800 [thread overview]
Message-ID: <B633F743-147D-46DD-B371-782F118A921F@gmail.com> (raw)
In-Reply-To: <CAP71Wjx4UGYsRTCC+PDWrPMeLP8cO+yayvTS3g9p=VBWvtUQJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
> On Feb 9, 2016, at 11:41 AM, Nicolas Dechesne <nicolas.dechesne@linaro.org> wrote:
>
> On Tue, Feb 9, 2016 at 8:04 PM, Khem Raj <raj.khem@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.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-02-09 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 9:13 [PATCH 0/4] Crypto dependency fixes Jussi Kukkonen
2016-02-09 9:24 ` [PATCH 1/4] systemd: Don't depend on gcrypt unnecessarily Jussi Kukkonen
2016-02-09 9:24 ` [PATCH 2/4] wpa-supplicant: Only depend on libgcrypt when needed Jussi Kukkonen
2016-02-09 9:24 ` [PATCH 3/4] libsoup-2.4: Remove unnecessary gnutls dependency Jussi Kukkonen
2016-02-09 9:24 ` [PATCH 4/4] xserver-xorg: Add PACKAGECONFIG for crypto libraries Jussi Kukkonen
2016-02-09 9:39 ` Nicolas Dechesne
2016-02-09 17:54 ` Khem Raj
2016-02-09 17:58 ` Burton, Ross
2016-02-09 19:04 ` Khem Raj
2016-02-09 19:41 ` Nicolas Dechesne
2016-02-09 21:21 ` Khem Raj [this message]
2016-02-09 18:04 ` Mark Hatle
2016-02-10 8:25 ` Jussi Kukkonen
2016-02-10 14:44 ` Mark Hatle
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=B633F743-147D-46DD-B371-782F118A921F@gmail.com \
--to=raj.khem@gmail.com \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@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.