From: Khem Raj <raj.khem@gmail.com>
To: Ross Burton <ross.burton@intel.com>
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 11:04:42 -0800 [thread overview]
Message-ID: <CAMKF1srP19D1Vg1Nvg5nbcqGp_xGLw=m8XFRiF6x659ixKZJBg@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LaLWz6=kt2D7B4q_9B5atfBEoTt7Og+_HqBoB98ax+RFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Feb 9, 2016 9:58 AM, "Burton, Ross" <ross.burton@intel.com> wrote:
>
>
> On 9 February 2016 at 17:54, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> > 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.
>
>
> Personally I'm not convinced that two recipes currently sharing a small
piece of configure code warrants a global configuration.
Think of crypto policy point of view
>
> Ross
[-- Attachment #2: Type: text/html, Size: 931 bytes --]
next prev parent reply other threads:[~2016-02-09 19:04 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 [this message]
2016-02-09 19:41 ` Nicolas Dechesne
2016-02-09 21:21 ` Khem Raj
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='CAMKF1srP19D1Vg1Nvg5nbcqGp_xGLw=m8XFRiF6x659ixKZJBg@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 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.