>> I think kernel and uboot are not bundled into image but kernel modules are why >> module-init-tools does not appear there might be a bug
Yes, that is technically of course correct. However, the idea of package.manifest and license.manifest should be to provide a list of everything that goes into the distribution together with the licenses. That's what one needs to provide to customers. And the image recipe has these items as dependencies. I would think that anything that is a runtime dependency of an image should show up in the manifests. task-core-boot is a runtime dependency of core-image-minimal. Interestingly, virtual/kernel is not a runtime dependency of task-core-boot but it is a build-time dependency. From the view of the build system that is correct and sufficient. It creates the kernel but of course the kernel is not included with the root file system image. It looks to me as if the class creating the licensing manifest evaluates the runtime dependencies which is not sufficient. That explains the kernel. But it does not explain module-init-tools, as you say. Checking reverse dependencies of module-init-tools shows nothing depends on them. So how do they get included with the root fs in the first place? Another strange thing I cannot make sense of is that linux-yocto runtime depends on python, perl, elfutils, kernel-base and kernel-image. :rjs
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
