From: Andrei Gherzan <andrei@gherzan.ro>
To: Saul Wold <sgw@linux.intel.com>
Cc: Andrei Gherzan <andrei.gherzan@windriver.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] wpa-supplicant - pulls GPLv3 license rpm in a non-GPLv3 build (libgnutls-extra)
Date: Thu, 05 Jan 2012 18:41:06 +0200 [thread overview]
Message-ID: <4F05D2A2.4010603@gherzan.ro> (raw)
In-Reply-To: <4F0396AA.3070901@linux.intel.com>
On 01/04/2012 02:00 AM, Saul Wold wrote:
> On 12/29/2011 02:22 AM, Andrei Gherzan wrote:
>> From: Andrei Gherzan<andrei.gherzan@windriver.com>
>>
>> Two different defconfigs are chosen, one for "with GPLv3 build" and
>> one for "without".
>> In this way, libgnutls-extra is not pulled in a non-GPLv3 build.
>>
>> [YOCTO #1845]
>>
>> Signed-off-by: Andrei Gherzan<andrei@gherzan.ro>
>> ---
>> .../wpa-supplicant/defconfig.inc | 4 +
>> .../wpa-supplicant-0.7.3/defconfig-gnutls-nogplv3 | 409
>> ++++++++++++++++++++
>> .../wpa-supplicant/wpa-supplicant-0.7.inc | 7 +-
>> 3 files changed, 418 insertions(+), 2 deletions(-)
>> create mode 100644
>> meta/recipes-connectivity/wpa-supplicant/defconfig.inc
>> create mode 100644
>> meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-0.7.3/defconfig-gnutls-nogplv3
>>
>
> Merged into OE-Core as coded here, but would be willing to get a new
> patch that removes the need for gnutls and the nogplv3 workaround.
>
> Thanks
> Sau!
Done.
[PATCH] wpa-supplicant: Patch this recipe order to remove
duplicate defconfig file (Andrei Gherzan)
prev parent reply other threads:[~2012-01-05 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 10:22 [PATCH] wpa-supplicant - pulls GPLv3 license rpm in a non-GPLv3 build (libgnutls-extra) Andrei Gherzan
2012-01-04 0:00 ` Saul Wold
2012-01-05 16:41 ` Andrei Gherzan [this message]
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=4F05D2A2.4010603@gherzan.ro \
--to=andrei@gherzan.ro \
--cc=andrei.gherzan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.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.