1. local.conf contains: COPY_LIC_MANIFEST = "1" COPY_LIC_DIRS = "1" 2. linux-firmware-ralink is added to image 3. If you check /usr/share/common-licenses/linux-firmware-ralink, it has licenses for all the firmware packages. license.manifest shows "LICENSE: Firmware-ralink-firmware" for the linux-firmware-ralink package 4. If you check /usr/share/common-licenses/linux-firmware-ralink-license, it has licenses for all the firmware packages. license.manifest shows "LICENSE: Firmware-Abilis & [...] & Firmware-xc5000c & WHENCE". So we need to do the following: * License for each linux-firmware-*-license package should be set correctly * Copy only the licenses for a package to the package's licenses directory and not the licenses for the recipe (which will have the licenses of all the packages)
Seems that the linux-firmware base package has an RDEPENDS on the generic linux-firmware-license package which includes all the licenses. Still digging
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=77a9472a4b4ff2daa9171eaae9ee10f1f8527a0d
Not completely fixed. The licenses directory still has licenses for all the firmware packages in: * /usr/share/common-licenses * /usr/share/common-licenses/linux-firmware-ralink * /usr/share/common-licenses/linux-firmware-ralink-license
Ok, so a little more research, the Manifest is generated on way based on the actual packages installed on the target rootfs. The License Directory is copied from the licenses provided by the recipe (so not on a package basis), to change this would require a pretty good re-write in the license.bbclass. THis actually affects all packages that might have multiple licenses, but only ship limited licneses in each package. Unless this is really urgent, I am going to close this one and will re-open a more general bug against license.bbclass
So we have fixed part of the problem that pertains to linux-firwmare license packages having the incorrect licenses. There is an problem that is generic to all packages that copies the working set of licenses to the target image based on the recipe's licenses vs the actual installed packages. A new bug#10325 has been created to address this in 2.3