[OE-core] [poky] [PATCH 0/7] Non-GPLv3 Changes & a dependency Fix

[Mark Hatle]

On 3/21/11 10:51 AM, Richard Purdie wrote:
> 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 at 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 at 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?

I think it's important to keep in mind that the responsibilities for
redistribution/repackaging really are up to the end user (of OE-core) and their
lawyer's interpretation of the license.

As Richard mentioned, our goal is specifically to keep any code (that we know
of) that is GPLv3/LGPLv3 off of the target system via the exclude license
feature.  (Which can also be used to target other license types.)

Source distribution and such is still the responsibility of the (OE-core)
end-user and their lawyers to determine.  What we did might be good enough, and
might not..

--Mark

> Cheers,
> 
> Richard
> 
> 
> 
> _______________________________________________
> poky mailing list
> poky at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky