All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Christopher Larson" <clarson@kergoth.com>,
	"Eric Bénard" <eric@eukrea.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] About GPLv2's native recipe
Date: Mon, 26 Jan 2015 09:17:20 +0800	[thread overview]
Message-ID: <54C595A0.8070702@windriver.com> (raw)
In-Reply-To: <CABcZANn4U+z7J7VxYRz_LomC2WGSFnErjz7opEQnG-Gbuh8FhA@mail.gmail.com>



On 01/26/2015 06:39 AM, Christopher Larson wrote:
>
> On Sun, Jan 25, 2015 at 2:18 PM, Eric Bénard <eric@eukrea.com
> <mailto:eric@eukrea.com>> wrote:
>
>     Le Fri, 23 Jan 2015 10:12:16 +0800,
>     Robert Yang <liezhi.yang@windriver.com <mailto:liezhi.yang@windriver.com>> a
>     écrit :
>     > We have several GPLv2 recipes such asm4-native_1.4.9.bb <http://m4-native_1.4.9.bb>, while we also
>     > have GPLv3'sm4-native_1.4.17.bb <http://m4-native_1.4.17.bb>, I think that we can remove
>     >m4-native_1.4.9.bb <http://m4-native_1.4.9.bb> if the target m4_1.4.9.bb
>     <http://m4_1.4.9.bb> builds well ?
>     >
>     > I'd like to remove it because we don't build the lower native version by
>     > default, and we don't know whether it works or when it would fail.
>     >
>     if you want to build a system without GPLv3 ("supported for only
>     minimal and base images" as stated in the manual) you may need GPLv2
>     tools :
>     http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-images
>     INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3.0"
>
>
> GPLv3 native tools will still be used in such a build, as far as I know, just
> not the target ones.

Yes, you're right.

Thanks for the reply everyone, I will address your concerns, try to
remove some recipes and send patches out.

// Robert


> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics


      reply	other threads:[~2015-01-26  1:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  2:12 [RFC] About GPLv2's native recipe Robert Yang
2015-01-23 12:47 ` Otavio Salvador
2015-01-23 16:24   ` Christopher Larson
2015-01-23 16:29     ` Otavio Salvador
2015-01-23 17:04   ` akuster808
2015-01-23 17:09     ` Paul Eggleton
2015-01-25 21:18 ` Eric Bénard
2015-01-25 22:39   ` Christopher Larson
2015-01-26  1:17     ` Robert Yang [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=54C595A0.8070702@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=clarson@kergoth.com \
    --cc=eric@eukrea.com \
    --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.