From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [poky] [PATCH 0/2] GPLv2 versions of m4 & bison
Date: Wed, 16 Mar 2011 20:20:46 -0500 [thread overview]
Message-ID: <4D8161EE.4050809@windriver.com> (raw)
In-Reply-To: <4D815D7F.3070304@mlbassoc.com>
Yes, these are alternative versions purely for licensing. There is a target
"poky-image-basic" that is our goal for allowing both (modern) licensing, and
non-(L)GPLv3 licensing. Anything outside (above and beyond) that is not part of
the plan.
The goal is to allow people to be able to produce a "basic", command line
oriented system that does not require (L)GPLv3 components.
(X is not part of the basic image, but X should be fine as well, since it's the
MIT-X licensing...)
--Mark
On 3/16/11 8:01 PM, Gary Thomas wrote:
> On 03/16/2011 03:03 PM, Nitin A Kamble wrote:
>> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>>
>> These commits adds GPLv2 versions of m4& bison recipes.
>>
>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>> Branch: nitin/misc
>> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
>>
>> Thanks,
>> Nitin A Kamble<nitin.a.kamble@intel.com>
>> ---
>>
>>
>> Nitin A Kamble (2):
>> bison: bring back GPLv2 version 2.3 of bison recipe
>> m4: bring back GPLv2 version 1.4.9 of m4 recipe
>>
>> .../bison/bison/bison-2.3_m4.patch | 590 ++++++++++++++++++++
>> meta/recipes-devtools/bison/bison_2.3.bb | 35 ++
>> meta/recipes-devtools/m4/m4-native_1.4.9.bb | 12 +
>> .../m4/m4/fix_for_circular_dependency.patch | 75 +++
>> meta/recipes-devtools/m4/m4_1.4.9.bb | 18 +
>> 5 files changed, 730 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-devtools/bison/bison/bison-2.3_m4.patch
>> create mode 100644 meta/recipes-devtools/bison/bison_2.3.bb
>> create mode 100644 meta/recipes-devtools/m4/m4-native_1.4.9.bb
>> create mode 100644 meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch
>> create mode 100644 meta/recipes-devtools/m4/m4_1.4.9.bb
>>
>
> Was this purely for licensing reasons? (just asking since there was no discussion on this list)
>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [OE-core] [PATCH 0/2] GPLv2 versions of m4 & bison
Date: Wed, 16 Mar 2011 20:20:46 -0500 [thread overview]
Message-ID: <4D8161EE.4050809@windriver.com> (raw)
In-Reply-To: <4D815D7F.3070304@mlbassoc.com>
Yes, these are alternative versions purely for licensing. There is a target
"poky-image-basic" that is our goal for allowing both (modern) licensing, and
non-(L)GPLv3 licensing. Anything outside (above and beyond) that is not part of
the plan.
The goal is to allow people to be able to produce a "basic", command line
oriented system that does not require (L)GPLv3 components.
(X is not part of the basic image, but X should be fine as well, since it's the
MIT-X licensing...)
--Mark
On 3/16/11 8:01 PM, Gary Thomas wrote:
> On 03/16/2011 03:03 PM, Nitin A Kamble wrote:
>> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>>
>> These commits adds GPLv2 versions of m4& bison recipes.
>>
>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>> Branch: nitin/misc
>> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
>>
>> Thanks,
>> Nitin A Kamble<nitin.a.kamble@intel.com>
>> ---
>>
>>
>> Nitin A Kamble (2):
>> bison: bring back GPLv2 version 2.3 of bison recipe
>> m4: bring back GPLv2 version 1.4.9 of m4 recipe
>>
>> .../bison/bison/bison-2.3_m4.patch | 590 ++++++++++++++++++++
>> meta/recipes-devtools/bison/bison_2.3.bb | 35 ++
>> meta/recipes-devtools/m4/m4-native_1.4.9.bb | 12 +
>> .../m4/m4/fix_for_circular_dependency.patch | 75 +++
>> meta/recipes-devtools/m4/m4_1.4.9.bb | 18 +
>> 5 files changed, 730 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-devtools/bison/bison/bison-2.3_m4.patch
>> create mode 100644 meta/recipes-devtools/bison/bison_2.3.bb
>> create mode 100644 meta/recipes-devtools/m4/m4-native_1.4.9.bb
>> create mode 100644 meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch
>> create mode 100644 meta/recipes-devtools/m4/m4_1.4.9.bb
>>
>
> Was this purely for licensing reasons? (just asking since there was no discussion on this list)
>
next prev parent reply other threads:[~2011-03-17 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 21:03 [PATCH 0/2] GPLv2 versions of m4 & bison Nitin A Kamble
2011-03-16 21:03 ` [PATCH 2/2] m4: bring back GPLv2 version 1.4.9 of m4 recipe Nitin A Kamble
2011-03-16 21:03 ` [PATCH 1/2] bison: bring back GPLv2 version 2.3 of bison recipe Nitin A Kamble
2011-03-17 0:22 ` [PATCH 0/2] GPLv2 versions of m4 & bison Richard Purdie
2011-03-17 0:22 ` [OE-core] " Richard Purdie
2011-03-17 1:01 ` [poky] " Gary Thomas
2011-03-17 1:01 ` Gary Thomas
2011-03-17 1:20 ` Mark Hatle [this message]
2011-03-17 1:20 ` [OE-core] " Mark Hatle
2011-03-17 1:44 ` [poky] " Kamble, Nitin A
2011-03-17 1:44 ` Kamble, Nitin A
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=4D8161EE.4050809@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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.