Avoiding both GPLv3 and meta-gplv2 ?

Avoiding both GPLv3 and meta-gplv2 ?

[Irving ST]

Hello,

First time posting, apologies if I miss anything in the community guidelines.

I had some problems trying to make an image that contains no GPLv3
(due to corporate requirement) nor old GPLv2 software in meta-gplv2
(due to lack of support).

I tried getting a fresh checkout of poky and adding
INCOMPATIBLE_LICENSE in conf/local.conf , but I got the following
error:

ERROR: Nothing RPROVIDES 'make' (but
/home/irving/srcgit/poky/meta/recipes-core/zlib/zlib_1.2.11.bb,
/home/irving/srcgit/poky/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb
RDEPENDS on or otherwise requires it)
make was skipped: it has an incompatible license: GPLv3 & LGPLv2

I tried adding meta-gplv2 layer to bblayer.conf and the error
disappears. I was expecting the license restriction to apply to the
final image only, but my guess is I am also restricted from building
the cross compilation tools (which seems weird to me).

Is this layer required when building without GPLv3?
Is there any alternative I can try, or is my choice limited to either
using GPLv3 code vs outdated GPLv2 code?
If I have to use the meta-gplv2 layer, is there a way to restrict
anything inside this layer from being built into the image?

I tried to look for information on building a busybox-based image (vs
a GNU coreutils-based image) in the mega manual but didn’t find
anything specific.

Regards,
Irving

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Burton, Ross]

The make dependencies come from the ptest packages, so if you disable
ptest in your DISTRO_FEATURES then those should disappear.

Essentially doing a full build without any GPLv3 software *and* not
using old releases which are still GPLv2 is tricky.  I can only
suggest you don't use the meta-gpl2 layer (as you don't want the
recipes to be used) and use bbappends to disable pieces where
required.

Ross

On 1 May 2018 at 11:58, Irving ST <irving@ssfivy.com> wrote:
> Hello,
>
> First time posting, apologies if I miss anything in the community guidelines.
>
> I had some problems trying to make an image that contains no GPLv3
> (due to corporate requirement) nor old GPLv2 software in meta-gplv2
> (due to lack of support).
>
> I tried getting a fresh checkout of poky and adding
> INCOMPATIBLE_LICENSE in conf/local.conf , but I got the following
> error:
>
> ERROR: Nothing RPROVIDES 'make' (but
> /home/irving/srcgit/poky/meta/recipes-core/zlib/zlib_1.2.11.bb,
> /home/irving/srcgit/poky/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb
> RDEPENDS on or otherwise requires it)
> make was skipped: it has an incompatible license: GPLv3 & LGPLv2
>
> I tried adding meta-gplv2 layer to bblayer.conf and the error
> disappears. I was expecting the license restriction to apply to the
> final image only, but my guess is I am also restricted from building
> the cross compilation tools (which seems weird to me).
>
> Is this layer required when building without GPLv3?
> Is there any alternative I can try, or is my choice limited to either
> using GPLv3 code vs outdated GPLv2 code?
> If I have to use the meta-gplv2 layer, is there a way to restrict
> anything inside this layer from being built into the image?
>
> I tried to look for information on building a busybox-based image (vs
> a GNU coreutils-based image) in the mega manual but didn’t find
> anything specific.
>
> Regards,
> Irving
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Anuj Mittal]

On 05/01/2018 06:58 PM, Irving ST wrote:
> Hello,
> 
> First time posting, apologies if I miss anything in the community guidelines.
> 
> I had some problems trying to make an image that contains no GPLv3
> (due to corporate requirement) nor old GPLv2 software in meta-gplv2
> (due to lack of support).
> 
> I tried getting a fresh checkout of poky and adding
> INCOMPATIBLE_LICENSE in conf/local.conf , but I got the following
> error:
> 
> ERROR: Nothing RPROVIDES 'make' (but
> /home/irving/srcgit/poky/meta/recipes-core/zlib/zlib_1.2.11.bb,
> /home/irving/srcgit/poky/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb
> RDEPENDS on or otherwise requires it)
> make was skipped: it has an incompatible license: GPLv3 & LGPLv2
> 
> I tried adding meta-gplv2 layer to bblayer.conf and the error
> disappears. I was expecting the license restriction to apply to the
> final image only, but my guess is I am also restricted from building
> the cross compilation tools (which seems weird to me).

You can grep the license.manifest in ./tmp/deploy/licenses to see what
is being included in the final image.

I think the poky core-image-minimal image can be built without
meta-gplv2 and non gplv3 components.

Thanks,
Anuj

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Paul Eggleton]

On Wednesday, 2 May 2018 12:07:42 AM NZST Burton, Ross wrote:
> The make dependencies come from the ptest packages, so if you disable
> ptest in your DISTRO_FEATURES then those should disappear.
> 
> Essentially doing a full build without any GPLv3 software *and* not
> using old releases which are still GPLv2 is tricky.  I can only
> suggest you don't use the meta-gpl2 layer (as you don't want the
> recipes to be used) and use bbappends to disable pieces where
> required.

We probably need some sort of whitepaper on how to do that, it doesn't look 
like our manuals cover it in sufficient detail. Any volunteers ? ;)

One other thing worth mentioning is that there has been some discussion a 
while ago about a better plan to handle this, in the form of providing a set 
of recipes for BSD-licensed replacements for GPLv3 components built for the 
target instead of old GPLv2 ones. I don't know if anyone is actively working 
on that though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Andre McCurdy]

On Tue, May 1, 2018 at 3:10 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Wednesday, 2 May 2018 12:07:42 AM NZST Burton, Ross wrote:
>> The make dependencies come from the ptest packages, so if you disable
>> ptest in your DISTRO_FEATURES then those should disappear.
>>
>> Essentially doing a full build without any GPLv3 software *and* not
>> using old releases which are still GPLv2 is tricky.  I can only
>> suggest you don't use the meta-gpl2 layer (as you don't want the
>> recipes to be used) and use bbappends to disable pieces where
>> required.
>
> We probably need some sort of whitepaper on how to do that, it doesn't look
> like our manuals cover it in sufficient detail. Any volunteers ? ;)

Does "Blacklist GPLv3, don't use meta-gplv2, fix any issues you may
run into" need a whitepaper? Or is there more to it than that?

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Paul Eggleton]

On Wednesday, 2 May 2018 11:54:00 AM NZST Andre McCurdy wrote:
> On Tue, May 1, 2018 at 3:10 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > On Wednesday, 2 May 2018 12:07:42 AM NZST Burton, Ross wrote:
> >> The make dependencies come from the ptest packages, so if you disable
> >> ptest in your DISTRO_FEATURES then those should disappear.
> >>
> >> Essentially doing a full build without any GPLv3 software *and* not
> >> using old releases which are still GPLv2 is tricky.  I can only
> >> suggest you don't use the meta-gpl2 layer (as you don't want the
> >> recipes to be used) and use bbappends to disable pieces where
> >> required.
> >
> > We probably need some sort of whitepaper on how to do that, it doesn't
> > look like our manuals cover it in sufficient detail. Any volunteers ? ;)
> 
> Does "Blacklist GPLv3, don't use meta-gplv2, fix any issues you may
> run into" need a whitepaper? Or is there more to it than that?

Apart from "disable ptest" as Ross pointed out, I would assume that's all 
there is to it - but right now aside from asking here there's really no way 
for someone to know that that's the best available way of handling it, so I 
think it's worth documenting somewhere.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Andre McCurdy]

On Tue, May 1, 2018 at 4:59 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Wednesday, 2 May 2018 11:54:00 AM NZST Andre McCurdy wrote:
>> On Tue, May 1, 2018 at 3:10 PM, Paul Eggleton
>> <paul.eggleton@linux.intel.com> wrote:
>> > On Wednesday, 2 May 2018 12:07:42 AM NZST Burton, Ross wrote:
>> >> The make dependencies come from the ptest packages, so if you disable
>> >> ptest in your DISTRO_FEATURES then those should disappear.
>> >>
>> >> Essentially doing a full build without any GPLv3 software *and* not
>> >> using old releases which are still GPLv2 is tricky.  I can only
>> >> suggest you don't use the meta-gpl2 layer (as you don't want the
>> >> recipes to be used) and use bbappends to disable pieces where
>> >> required.
>> >
>> > We probably need some sort of whitepaper on how to do that, it doesn't
>> > look like our manuals cover it in sufficient detail. Any volunteers ? ;)
>>
>> Does "Blacklist GPLv3, don't use meta-gplv2, fix any issues you may
>> run into" need a whitepaper? Or is there more to it than that?
>
> Apart from "disable ptest" as Ross pointed out, I would assume that's all
> there is to it - but right now aside from asking here there's really no way
> for someone to know that that's the best available way of handling it, so I
> think it's worth documenting somewhere.

Yes, OK. I hadn't realised ptest is enabled by default in poky (!?!).

  http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?id=9381b2d2bddf9f67cf57b0718cf99e45805125fa

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Burton, Ross]

On 2 May 2018 at 01:41, Andre McCurdy <armccurdy@gmail.com> wrote:
> On Tue, May 1, 2018 at 4:59 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
>> On Wednesday, 2 May 2018 11:54:00 AM NZST Andre McCurdy wrote:
>>> On Tue, May 1, 2018 at 3:10 PM, Paul Eggleton
>>> <paul.eggleton@linux.intel.com> wrote:
>>> > On Wednesday, 2 May 2018 12:07:42 AM NZST Burton, Ross wrote:
>>> >> The make dependencies come from the ptest packages, so if you disable
>>> >> ptest in your DISTRO_FEATURES then those should disappear.
>>> >>
>>> >> Essentially doing a full build without any GPLv3 software *and* not
>>> >> using old releases which are still GPLv2 is tricky.  I can only
>>> >> suggest you don't use the meta-gpl2 layer (as you don't want the
>>> >> recipes to be used) and use bbappends to disable pieces where
>>> >> required.
>>> >
>>> > We probably need some sort of whitepaper on how to do that, it doesn't
>>> > look like our manuals cover it in sufficient detail. Any volunteers ? ;)
>>>
>>> Does "Blacklist GPLv3, don't use meta-gplv2, fix any issues you may
>>> run into" need a whitepaper? Or is there more to it than that?
>>
>> Apart from "disable ptest" as Ross pointed out, I would assume that's all
>> there is to it - but right now aside from asking here there's really no way
>> for someone to know that that's the best available way of handling it, so I
>> think it's worth documenting somewhere.
>
> Yes, OK. I hadn't realised ptest is enabled by default in poky (!?!).
>
>   http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?id=9381b2d2bddf9f67cf57b0718cf99e45805125fa

Poky is primarily a vehicle for testing the Yocto Project software, so
it follows that it enables ptest for QA purposes.

Ross

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Irving ST]

On Wed, May 2, 2018 at 7:01 PM, Burton, Ross <ross.burton@intel.com> wrote:
> On 2 May 2018 at 01:41, Andre McCurdy <armccurdy@gmail.com> wrote:
>> On Tue, May 1, 2018 at 4:59 PM, Paul Eggleton
>> <paul.eggleton@linux.intel.com> wrote:
>>> On Wednesday, 2 May 2018 11:54:00 AM NZST Andre McCurdy wrote:
>>>> On Tue, May 1, 2018 at 3:10 PM, Paul Eggleton
>>>> <paul.eggleton@linux.intel.com> wrote:
>>>> > On Wednesday, 2 May 2018 12:07:42 AM NZST Burton, Ross wrote:
>>>> >> The make dependencies come from the ptest packages, so if you disable
>>>> >> ptest in your DISTRO_FEATURES then those should disappear.
>>>> >>
>>>> >> Essentially doing a full build without any GPLv3 software *and* not
>>>> >> using old releases which are still GPLv2 is tricky.  I can only
>>>> >> suggest you don't use the meta-gpl2 layer (as you don't want the
>>>> >> recipes to be used) and use bbappends to disable pieces where
>>>> >> required.
>>>> >
>>>> > We probably need some sort of whitepaper on how to do that, it doesn't
>>>> > look like our manuals cover it in sufficient detail. Any volunteers ? ;)
>>>>
>>>> Does "Blacklist GPLv3, don't use meta-gplv2, fix any issues you may
>>>> run into" need a whitepaper? Or is there more to it than that?
>>>
>>> Apart from "disable ptest" as Ross pointed out, I would assume that's all
>>> there is to it - but right now aside from asking here there's really no way
>>> for someone to know that that's the best available way of handling it, so I
>>> think it's worth documenting somewhere.
>>
>> Yes, OK. I hadn't realised ptest is enabled by default in poky (!?!).
>>
>>   http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?id=9381b2d2bddf9f67cf57b0718cf99e45805125fa
>
> Poky is primarily a vehicle for testing the Yocto Project software, so
> it follows that it enables ptest for QA purposes.
>
> Ross

Hi all,

Thank you for your help and explanations. Unfortunately just removing
ptest doesn't make it build.
This is the error when I tried bitbake core-image-minimal:

ERROR: Nothing PROVIDES 'readline' (but
/home/irving/srcgit/poky/meta/recipes-devtools/python/python3_3.5.5.bb
DEPENDS on or otherwise requires it)
readline was skipped: it has an incompatible license: GPLv3+
NOTE: Runtime target 'nativesdk-dnf' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nativesdk-dnf',
'nativesdk-librepo', 'nativesdk-python3', 'python3', 'readline']
NOTE: Runtime target 'nativesdk-packagegroup-sdk-host' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['nativesdk-packagegroup-sdk-host', 'nativesdk-dnf',
'nativesdk-librepo', 'nativesdk-python3', 'python3', 'readline']
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal',
'nativesdk-packagegroup-sdk-host', 'nativesdk-dnf',
'nativesdk-librepo', 'nativesdk-python3', 'python3', 'readline']


This is the error when I tried bitbake core-image-base:

ERROR: Nothing PROVIDES 'gdbm' (but
/home/irving/srcgit/poky/meta/recipes-devtools/python/python3_3.5.5.bb,
/home/irving/srcgit/poky/meta/recipes-devtools/perl/perl_5.24.1.bb
DEPENDS on or otherwise requires it)
gdbm was skipped: it has an incompatible license: GPLv3
NOTE: Runtime target 'gdb-cross-canadian-i586' is unbuildable, removing...
Missing or unbuildable dependency chain was:
['gdb-cross-canadian-i586', 'nativesdk-python3', 'python3', 'gdbm']
NOTE: Runtime target 'packagegroup-cross-canadian-qemux86' is
unbuildable, removing...
Missing or unbuildable dependency chain was:
['packagegroup-cross-canadian-qemux86', 'gdb-cross-canadian-i586',
'nativesdk-python3', 'python3', 'gdbm']
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base',
'packagegroup-cross-canadian-qemux86', 'gdb-cross-canadian-i586',
'nativesdk-python3', 'python3', 'gdbm']

Since doing this seems trickier than I expected then I might have to
develop with meta-gplv2 for now and revisit this at a later date.

Regards,
Irving

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Alexander Kanavin]

On 05/02/2018 04:53 PM, Irving ST wrote:
> Thank you for your help and explanations. Unfortunately just removing
> ptest doesn't make it build.
> This is the error when I tried bitbake core-image-minimal:
> 
> ERROR: Nothing PROVIDES 'readline' (but
> /home/irving/srcgit/poky/meta/recipes-devtools/python/python3_3.5.5.bb
> ERROR: Nothing PROVIDES 'gdbm' (but
> /home/irving/srcgit/poky/meta/recipes-devtools/python/python3_3.5.5.bb,
> /home/irving/srcgit/poky/meta/recipes-devtools/perl/perl_5.24.1.bb
> DEPENDS on or otherwise requires it)

'readline' dependency can be easily disabled in python via 
PACKAGECONFIG. gdbm might be trickier, but I believe it's optional as well.

Alex

Re: Avoiding both GPLv3 and meta-gplv2 ?

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

On 2 May 2018 at 14:58, Alexander Kanavin <alexander.kanavin@linux.intel.com
> wrote:

> On 05/02/2018 04:53 PM, Irving ST wrote:
>
>> Thank you for your help and explanations. Unfortunately just removing
>> ptest doesn't make it build.
>> This is the error when I tried bitbake core-image-minimal:
>>
>> ERROR: Nothing PROVIDES 'readline' (but
>> /home/irving/srcgit/poky/meta/recipes-devtools/python/python3_3.5.5.bb
>> ERROR: Nothing PROVIDES 'gdbm' (but
>> /home/irving/srcgit/poky/meta/recipes-devtools/python/python3_3.5.5.bb,
>> /home/irving/srcgit/poky/meta/recipes-devtools/perl/perl_5.24.1.bb
>> DEPENDS on or otherwise requires it)
>>
>
> 'readline' dependency can be easily disabled in python via PACKAGECONFIG.
> gdbm might be trickier, but I believe it's optional as well.
>

Note that this readline PACKAGECONFIG is in sumo/master, so you'll need to
cherrypick it if you're not using that.

gdbm is a little more fiddly but it can be done, I had a proof of concept
but didn't finish it.  Start by removing gdbm from DEPENDS in a bbappend
and see what breaks...

Ross

[-- Attachment #2: Type: text/html, Size: 1946 bytes --]