Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: poky@yoctoproject.org,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [PATCH 0/7] Non-GPLv3 Changes & a dependency Fix
Date: Mon, 21 Mar 2011 15:51:28 +0000	[thread overview]
Message-ID: <1300722688.30423.3745.camel@rex> (raw)
In-Reply-To: <20110321062422.GB5575@denix.org>

On Mon, 2011-03-21 at 02:24 -0400, Denys Dmytriyenko wrote:
> On Thu, Mar 17, 2011 at 05:47:35PM +0000, Richard Purdie wrote:
> > On Thu, 2011-03-17 at 02:58 -0700, Saul Wold wrote:
> > > From: Saul Wold <sgw@linux.intel.com>
> > >
> > > This set of changes enables both poky-image-minimal and poky-image-basic
> > > to build non-gplv3 core image. These are bound for bernard
> > > 
> > > There is also a fix for the gnome-vfs dependency on ACL. This is
> > > a potential build stopper and should be considered for bernard
> > > 
> > > Pull URL: git://git.openembedded.org/openembedded-core-contrib
> > >   Branch: sgw/non-gplv3
> > >   Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/non-gplv3
> > > 
> > > Thanks,
> > >     Saul Wold <sgw@linux.intel.com>
> > > ---
> > > 
> > > 
> > > Saul Wold (7):
> > >   util-linux: Setup for GPLv2 Recipe
> > 
> > I don't like this patch at all, there are some typos in it and some
> > other issues. Too risky for bernard for sure. I'm leaving it for now.
> 
> FYI, in Arago I had to repackage util-linux-ng source tarball w/o lscpu pieces 
> to completely avoid GPLv3, instead of removing them on the fly... In case when 
> said source tarball needs to be mirrored or distributed with the build.

The main point is to ensure the runtime is GPLv3 free. With those files
removed, that is the case. If you share a mirror with some GPLv3 code in
it, it has a very different effect licensing wise compared to v3
binaries on a system. I'm not a lawyer though and I'd be interested to
know if you've heard a different interpretation of the license?

> And, BTW, there is one more little script under GPLv3 - tests/ts/lscpu/lscpu

As Nitin replied, I thought that was removed already?

Cheers,

Richard






  parent reply	other threads:[~2011-03-21 15:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17  9:58 [PATCH 0/7] Non-GPLv3 Changes & a dependency Fix Saul Wold
2011-03-17  9:58 ` [PATCH 1/7] util-linux: Setup for GPLv2 Recipe Saul Wold
2011-03-17  9:58 ` [PATCH 2/7] extended tasks: move binutils from basic to lsb Saul Wold
2011-03-17  9:58 ` [PATCH 3/7] poky-image-basic: remove POKY_BASE_INSTALL Saul Wold
2011-03-17  9:58 ` [PATCH 4/7] poky.conf: add additional Libraries to the LGPLv2 Whitelist Saul Wold
2011-03-17  9:58 ` [PATCH 5/7] poky.conf: remove gnome-common from WHITELIST_GPLV3 Saul Wold
2011-03-17  9:58 ` [PATCH 6/7] gettext: Upgrade GPLv2 version to 0.16.1 Saul Wold
2011-03-17  9:58 ` [PATCH 7/7] gnome-vfs: add DEPENDS for acl Saul Wold
2011-03-17 17:47 ` [poky] [PATCH 0/7] Non-GPLv3 Changes & a dependency Fix Richard Purdie
2011-03-21  6:24   ` Denys Dmytriyenko
2011-03-21 15:35     ` Kamble, Nitin A
2011-03-21 15:51     ` Richard Purdie [this message]
2011-03-21 16:40       ` Mark Hatle

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