> -----Original Message----- > From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] > Sent: Monday, April 20, 2015 4:20 PM > To: Huang, Jie (Jackie) > Cc: openembedded-core@lists.openembedded.org > Subject: Re: [OE-core] [PATCH 0/2] linux-firmware: fix the mess of licenses > > On Monday 20 April 2015 07:33:34 Huang, Jie wrote: > > > -----Original Message----- > > > From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] > > > Sent: Friday, April 17, 2015 7:02 PM > > > To: Huang, Jie (Jackie) > > > Cc: openembedded-core@lists.openembedded.org > > > Subject: Re: [OE-core] [PATCH 0/2] linux-firmware: fix the mess of > > > licenses > > > > > > Hi Jackie, > > > > > > On Monday 13 April 2015 10:17:19 jackie.hu...@windriver.com wrote: > > > > From: Jackie Huang <jackie.hu...@windriver.com> > > > > > > > > linux-firmware includes many firmwares and each firmware has their > > > > own license, previously the LICENSE is set to "Proprietary" and > > > > some firmware is split out to separate package such as > > > > linux-firmware-radeon and LICENSE_linux-firmware-radeon is set to > > > > "Firmware-radeon", but there is no license file in the > > > > common-licenses, so we got a lot warnings> > > > like: > > > > WARNING: The license listed Firmware-radeon was not in the > > > > licenses collected for linux-firmware > > > > > > > > These include adding the missing license files and re-orgnize the > > > > codes to fix the warnings and avoid the mess. > > > > > > So doing this cleanup is good, thanks; but I was wondering if we > > > needed an alternative approach for linux-firmware. Most of the > > > licenses in it aren't in any way common, and new ones will be added > > > from time to time, requiring us to not only update the recipe > > > (probably unavoidable) but also add the licenses to the common > > > license directory. Is there any way we could make it so we at least > > > only have to update the recipe and dispense with the need to add a > > > bunch of common license files that are only applicable to linux-firmware? > > > > Maybe we can keep those linux-firmware licenses in the recipe > > directory instead of COMMON_LICENSE_DIR and add LICENSE_PATH += > > "${COREBASE}/meta/ recipes-kernel/linux-firmware/files"? > > Could we go one step further and copy the license files from the fetched > source rather than having to > add them to the recipe?
Yes, it's better, I will take a look if we can make this work. Thanks, Jackie > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
