Bug 1845

Summary: wpa-supplicant - GPLv3 license rpm present in a non-GPLv3 build
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Andrei Gherzan <andrei>
Component: coreAssignee: Andrei Gherzan <andrei>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, sgw
Version: unspecified   
Target Milestone: 1.2 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
gplv3 rpm shouldn't be pulled in a non-gplv3 build none

Description Andrei Gherzan 2011-12-19 06:05:10 UTC 
https://lists.yoctoproject.org/pipermail/poky/2011-December/007341.html

From gnutls bb file:

LICENSE = "GPLv3+ & LGPLv2.1+"
LICENSE_${PN} = "LGPLv2.1+"
LICENSE_${PN}-xx = "LGPLv2.1+"
LICENSE_${PN}-bin = "GPLv3+"
LICENSE_${PN}-extra = "GPLv3+"
LICENSE_${PN}-openssl = "GPLv3+"

In a core-image-minimal build with (INCOMPATIBLE_LICENSE = "GPLv3") and wpa-supplicant (has gnutls dependency), gnutls-extra is present in rootfs event if it has GPLv3 license.
Comment 1 Andrei Gherzan 2011-12-19 06:44:03 UTC 
If you look into wpa-supplicant-0.7.3/defconfig-gnutls you can see
there CONFIG_GNUTLS_EXTRA=y. Commenting out this CONFIG_GNUTLS_EXTRA=y
creates a build into which I do not have anymore the libraries from
the -extra rpm.
Comment 2 Andrei Gherzan 2011-12-21 07:17:29 UTC 
You can assign this bug to me. I will upload a patch as soon as my test  build will be finished.
Comment 3 Andrei Gherzan 2011-12-21 10:52:46 UTC 
Created attachment 306 [details]
gplv3 rpm shouldn't be pulled in a non-gplv3 build

I uploaded a patch for this bug. This solution checks if it is a non-GPLv3 build and install a specific defconfig accordingly.
Comment 4 Andrei Gherzan 2011-12-28 11:57:47 UTC 
I just realized that the subject was not clear enough so i edited it.
Comment 5 Andrei Gherzan 2011-12-30 03:31:44 UTC 
Patch submitted by email to openembedded-core list:

http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/015129.html
Comment 7 Andrei Gherzan 2012-01-05 13:41:46 UTC 
I simplified this problem by removing this config in both build cases.

Patch submitted.