Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/5] help2man-native: Add 1.36.4 (GPLv2) and 1.38.2 (GPLv3)
Date: Fri, 15 Jul 2011 23:47:02 +0100	[thread overview]
Message-ID: <1310770022.20015.1257.camel@rex> (raw)
In-Reply-To: <4E20BF61.3020901@mentor.com>

On Fri, 2011-07-15 at 15:29 -0700, Tom Rini wrote:
> On 07/15/2011 03:24 PM, Saul Wold wrote:
> > On 07/15/2011 03:03 PM, Tom Rini wrote:
> >> These are 'side ports' of current oe.dev versions.  PR is kept in sync
> >> but we drop out the target recipes in order to punt on potential perl
> >> problems.
> >>
> >> Signed-off-by: Tom Rini<tom_rini@mentor.com>
> >> ---
> >>   .../help2man/help2man-native_1.36.4.bb             |   26
> >> ++++++++++++++++++++
> >>   .../help2man/help2man-native_1.38.2.bb             |   24
> >> ++++++++++++++++++
> >>   2 files changed, 50 insertions(+), 0 deletions(-)
> >>   create mode 100644
> >> meta/recipes-devtools/help2man/help2man-native_1.36.4.bb
> >>   create mode 100644
> >> meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
> >>
> > 
> > Why do we need both versions?  Can't we just use the most current?
> 
> For the "I want no GPLv3" crowd.  This is a little more clear in oe.dev
> where we also build for the target but yes, different legal departments
> have different GPLv3 concerns so I think it makes sense in this case still.

We support limited GPLv2 functionality for the target. We don't do this
for the build tools since the compiler is GPLv3 for a start. We also
don't cover target development tools.

So I don't think we need the old version...

Cheers,

Richard





  parent reply	other threads:[~2011-07-15 22:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 22:03 [PATCH 0/5] Optionally trade required_utils for -native builds Tom Rini
2011-07-15 22:03 ` [PATCH 1/5] mercurial-native: Add 1.9 version Tom Rini
2011-07-15 22:14   ` Khem Raj
2011-07-15 22:22     ` Tom Rini
2011-07-15 22:03 ` [PATCH 2/5] bitbake.conf, sanity.bbclass: Make mercurial-native optional Tom Rini
2011-07-15 22:03 ` [PATCH 3/5] help2man-native: Add 1.36.4 (GPLv2) and 1.38.2 (GPLv3) Tom Rini
2011-07-15 22:24   ` Saul Wold
2011-07-15 22:29     ` Tom Rini
2011-07-15 22:41       ` Saul Wold
2011-07-15 22:47       ` Richard Purdie [this message]
2011-07-15 22:48   ` Richard Purdie
2011-07-15 22:53     ` Tom Rini
2011-07-18 22:13       ` Tom Rini
2011-07-19 12:17         ` Phil Blundell
2011-07-19 14:18           ` Tom Rini
2011-07-15 22:03 ` [PATCH 4/5] sanity.bbclass: Add help2man-native to ASSUME_PROVIDED if found Tom Rini
2011-07-15 22:03 ` [PATCH 5/5] autotools.bbclass: Add help2man-native to the main DEPENDS tree Tom Rini

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=1310770022.20015.1257.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox