At this point, we know how to use Poky and understand its main goal. It is time to understand the legal aspects of producing a Linux-based system that uses packages under different licenses.
We can configure Poky to generate the needed artifacts that should be shared as part of the copyleft compliance accomplishment process.
To help us to achieve copyleft compliance, Poky generates a license manifest during the image build located at build/tmp/deploy/licenses/<image_name-machine_name-datestamp>/.
To demonstrate this process, we use the core-image-full-cmdline image for the qemuarm machine. To start with our example, examine the files under build/tmp/deploy/licenses/core-image-full-cmdline-qemuarm-<datastamp>, which are as follows:
package.manifest: This lists all the packages into the image.license.manifest: This lists the names, versions, recipe names, and licenses for all packages. This file may be used for copyleft compliance...