All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Phil Blundell <philb@gnu.org>
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: Patch this recipe order to remove a duplicate defconfig file
Date: Thu, 05 Jan 2012 18:56:45 +0200	[thread overview]
Message-ID: <4F05D64D.4070906@gherzan.ro> (raw)
In-Reply-To: <1325781698.28005.132.camel@phil-desktop>

On 01/05/2012 06:41 PM, Phil Blundell wrote:
> On Thu, 2012-01-05 at 18:39 +0200, Andrei Gherzan wrote:
>> From: Andrei Gherzan<andrei.gherzan@windriver.com>
>>
>> Instead of having two defconfigs we can have only one and append this file with de specific
>> CONFIG if GPLv3 packages are allowed.
> As I said the other day, I think it would be better to just have one
> defconfig and turn off the GPLv3 stuff entirely.  Do you know of anybody
> who actually wants to use it?
>
> p.
>
>

Now about that extra config. The idea of having it into a build were 
gplv3 packages are allowed, was support for TLS/IA which was designed to 
be used in the EAP-TTLSv1
https://lists.yoctoproject.org/pipermail/poky/2011-December/007386.html

I will commit a change with just one defconfig which will be edited in 
bb file similar to this commit. Is this ok?




  parent reply	other threads:[~2012-01-05 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 16:39 [PATCH] wpa-supplicant: Patch this recipe order to remove a duplicate defconfig file Andrei Gherzan
2012-01-05 16:41 ` Phil Blundell
2012-01-05 16:44   ` Andrei Gherzan
2012-01-05 16:56   ` Andrei Gherzan [this message]
     [not found]   ` <4F05D5CB.2070404@windriver.com>
2012-01-05 17:00     ` Phil Blundell
2012-01-05 17:09       ` Andrei Gherzan

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=4F05D64D.4070906@gherzan.ro \
    --to=andrei@gherzan.ro \
    --cc=andrei.gherzan@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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.