How is the list in package.manifest derived?

How is the list in package.manifest derived?

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
Now I am looking for a list of everything that went into my image together
with the license information. The logical thing seems to be
${TMPDIR}/deploy/licenses/core-image-minimal-beagleboard-<timestamp>/package.manifest:

base-files
base-passwd
bash
busybox
busybox-syslog
busybox-udhcpc
initscripts
libc6
libgcc1
libtinfo5
libusb-1.0-0
libusb-compat
modutils-initscripts
ncurses-terminfo-base
netbase
pciutils-ids
sysvinit
sysvinit-inittab
sysvinit-pidof
task-core-boot
tinylogin
udev
udev-extraconf
udev-utils
update-alternatives-cworth
update-rc.d
usbutils-ids

However, I don't think this is everything that went into the image. I would
expect the kernel to be in the list as well as module-init-tools and
u-boot. Apparently package.manifest and the corresponding license.manifest
for an image target do not contain all the licensing information that a
device builder would need to give to the end customer. How is that list
created?

Rudi

[-- Attachment #2: Type: text/html, Size: 1381 bytes --]

Re: How is the list in package.manifest derived?

[Flanagan, Elizabeth]

On Tue, May 15, 2012 at 3:38 PM, Rudolf Streif <rudolf.streif@linux.com> wrote:
> I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
> Now I am looking for a list of everything that went into my image together
> with the license information. The logical thing seems to be
> ${TMPDIR}/deploy/licenses/core-image-minimal-beagleboard-<timestamp>/package.manifest:
>
> base-files
> base-passwd
> bash
> busybox
> busybox-syslog
> busybox-udhcpc
> initscripts
> libc6
> libgcc1
> libtinfo5
> libusb-1.0-0
> libusb-compat
> modutils-initscripts
> ncurses-terminfo-base
> netbase
> pciutils-ids
> sysvinit
> sysvinit-inittab
> sysvinit-pidof
> task-core-boot
> tinylogin
> udev
> udev-extraconf
> udev-utils
> update-alternatives-cworth
> update-rc.d
> usbutils-ids
>
> However, I don't think this is everything that went into the image. I would
> expect the kernel to be in the list as well as module-init-tools and u-boot.
> Apparently package.manifest and the corresponding license.manifest for an
> image target do not contain all the licensing information that a device
> builder would need to give to the end customer. How is that list created?

This list is created via license_create_manifest within
license.bbclass. I'm currently in the process of refactoring it quite
a bit so I'll look out for this issue.

It derives the list from list_installed_packages. Which means that
there may be an issue with that function. The way I'm planning on
doing it does not use list_installed_packages, however I'm going to
open a bug on it to verify that it is in fact returning an incomplete
list.

What would be helpful here is knowing what package type you're using.

-b

>
> Rudi
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release

Re: How is the list in package.manifest derived?

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]

Thanks for your response, Beth. I am using the default: RPM.

:rjs

On Tue, May 15, 2012 at 3:53 PM, Flanagan, Elizabeth <
elizabeth.flanagan@intel.com> wrote:

> On Tue, May 15, 2012 at 3:38 PM, Rudolf Streif <rudolf.streif@linux.com>
> wrote:
> > I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
> > Now I am looking for a list of everything that went into my image
> together
> > with the license information. The logical thing seems to be
> >
> ${TMPDIR}/deploy/licenses/core-image-minimal-beagleboard-<timestamp>/package.manifest:
> >
> > base-files
> > base-passwd
> > bash
> > busybox
> > busybox-syslog
> > busybox-udhcpc
> > initscripts
> > libc6
> > libgcc1
> > libtinfo5
> > libusb-1.0-0
> > libusb-compat
> > modutils-initscripts
> > ncurses-terminfo-base
> > netbase
> > pciutils-ids
> > sysvinit
> > sysvinit-inittab
> > sysvinit-pidof
> > task-core-boot
> > tinylogin
> > udev
> > udev-extraconf
> > udev-utils
> > update-alternatives-cworth
> > update-rc.d
> > usbutils-ids
> >
> > However, I don't think this is everything that went into the image. I
> would
> > expect the kernel to be in the list as well as module-init-tools and
> u-boot.
> > Apparently package.manifest and the corresponding license.manifest for an
> > image target do not contain all the licensing information that a device
> > builder would need to give to the end customer. How is that list created?
>
> This list is created via license_create_manifest within
> license.bbclass. I'm currently in the process of refactoring it quite
> a bit so I'll look out for this issue.
>
> It derives the list from list_installed_packages. Which means that
> there may be an issue with that function. The way I'm planning on
> doing it does not use list_installed_packages, however I'm going to
> open a bug on it to verify that it is in fact returning an incomplete
> list.
>
> What would be helpful here is knowing what package type you're using.
>
> -b
>
> >
> > Rudi
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
>
>
> --
> Elizabeth Flanagan
> Yocto Project
> Build and Release
>

[-- Attachment #2: Type: text/html, Size: 3133 bytes --]

Re: How is the list in package.manifest derived?

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

Related to that I have another question. If I use this recipe to create an
image

DESCRIPTION = "A small image with gcc"
IMAGE_INSTALL = "task-core-boot gcc"
LICENSE = "MIT"
inherit core-image

and call it myimage.bb

${TMPDIR}/deploy/icenses will contain a subdirectory named myimage.
However, the content of the directory is not, as I would love to have it, a
license.manifest and a package.manifest file but the MIT licensing
information.

What makes a recipe such as core-image-minimal.bb magically different from
myimage.bb so that the former includes the manifests? It does not seem to
be the content of the recipe.

:rjs

[-- Attachment #2: Type: text/html, Size: 950 bytes --]

Re: How is the list in package.manifest derived?

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

On Tuesday, May 15, 2012, Rudolf Streif <rudolf.streif@linux.com> wrote:
> I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
Now I am looking for a list of everything that went into my image together
with the license information. The logical thing seems to be
${TMPDIR}/deploy/licenses/core-image-minimal-beagleboard-<timestamp>/package.manifest:
> base-files
> base-passwd
> bash
> busybox
> busybox-syslog
> busybox-udhcpc
> initscripts
> libc6
> libgcc1
> libtinfo5
> libusb-1.0-0
> libusb-compat
> modutils-initscripts
> ncurses-terminfo-base
> netbase
> pciutils-ids
> sysvinit
> sysvinit-inittab
> sysvinit-pidof
> task-core-boot
> tinylogin
> udev
> udev-extraconf
> udev-utils
> update-alternatives-cworth
> update-rc.d
> usbutils-ids
> However, I don't think this is everything that went into the image. I
would expect the kernel to be in the list as well as module-init-tools and
u-boot. Apparently package.manifest and the corresponding license.manifest
for an image target do not contain all the licensing information that a
device builder would need to give to the end customer. How is that list
created?

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
> Rudi

[-- Attachment #2: Type: text/html, Size: 1551 bytes --]

Re: How is the list in package.manifest derived?

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]

>> 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

[-- Attachment #2: Type: text/html, Size: 1544 bytes --]