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 artifacts that should be shared as part of the copyleft compliance 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 will use the core-image-full-cmdline image for the qemuarm machine. To start with our example, look at the files under build/tmp/deploy/licenses/core-image-full-cmdline-qemuarm-<datastamp>, which are as follows:
image_license.manifest: This lists the recipe names, versions, licenses, and the files of packages that are available inbuild/tmp/deploy/image/<machine>but not installed insiderootfs. The most common examples...