Narcissus assembled BeagleBoard Validation Image

Hi,

As one of my tasks is to improve the validation image, I am trying to
understand what goes into it and what the sizes of the packages are.

I was trying to get a list of packages that go into a Narcissus built
image such as "validation gnome image", and was going over the list in
testlab.
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/tree/beagleboard/validation-GNOME-image/installed-package-sizes.txt

This list however is the size of the ipks themselves, and don't seem
to indicate what the size would be once uncompressed/installed.

What would be the easiest way for me to get a list of the final size
of each of the packages that go into such an image?

I have a script currently that unpacks the ipk and does a gzip -l
data.tar.gz to get it, but I feel that is quite space intensive,
although quick.

Hi,

As one of my tasks is to improve the validation image, I am trying to
understand what goes into it and what the sizes of the packages are.

I was trying to get a list of packages that go into a Narcissus built
image such as "validation gnome image", and was going over the list in
testlab.
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/tree/beagleboard/validation-GNOME-image/installed-package-sizes.txt

This list however is the size of the ipks themselves, and don't seem
to indicate what the size would be once uncompressed/installed.

What would be the easiest way for me to get a list of the final size
of each of the packages that go into such an image?

UBIfs also does compression, so the compressed sizes are a good indicator

As a next task, I also have to document how one could build the same
image using Bitbake instead of Narcissus.

I noticed the HTML form for the Narcissus form in the BeagleBoard
validation section is:
    <input type="checkbox" name="platform_packages"
value="task-base-extended task-beagleboard-validation-base
task-omap-drivers angstrom-task-gnome angstrom-gdm-autologin-hack
bash-sh midori gedit u-boot x-load vim vim-vimrc vim-syntax
kernel-modules libgles-omap3-x11demos bc-cube-x11 opencv-samples-dev">

This doesn't seem to be consistent with what's in
images/beagleboard-validation-gnome-image.bb in OpenEmbedded.

Inconsistent how?

Hi,

As one of my tasks is to improve the validation image, I am trying to
understand what goes into it and what the sizes of the packages are.

I was trying to get a list of packages that go into a Narcissus built
image such as "validation gnome image", and was going over the list in
testlab.
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/tree/beagleboard/validation-GNOME-image/installed-package-sizes.txt

This list however is the size of the ipks themselves, and don't seem
to indicate what the size would be once uncompressed/installed.

What would be the easiest way for me to get a list of the final size
of each of the packages that go into such an image?

UBIfs also does compression, so the compressed sizes are a good indicator

Sure.

Is there also a way to learn how much total space compressed or
otherwise, would installing a higher level package that has lots of
dependencies consume?

Like for example if I were to install gnome-desktop, how could I do
the calculation of the total size of all the packages it drags in?

The way I think it could be done is, by building a dependency tree
using "bitbake -g", and then finding the package sizes either by
building them or looking up testlab. Do you have any suggestions on
what could be a better way?

As a next task, I also have to document how one could build the same
image using Bitbake instead of Narcissus.

I noticed the HTML form for the Narcissus form in the BeagleBoard
validation section is:
<input type="checkbox" name="platform_packages"
value="task-base-extended task-beagleboard-validation-base
task-omap-drivers angstrom-task-gnome angstrom-gdm-autologin-hack
bash-sh midori gedit u-boot x-load vim vim-vimrc vim-syntax
kernel-modules libgles-omap3-x11demos bc-cube-x11 opencv-samples-dev">

This doesn't seem to be consistent with what's in
images/beagleboard-validation-gnome-image.bb in OpenEmbedded.

Inconsistent how?

It appears that there are packages such as those mentioned below, that
are in the above <input> list but are not built in the recipe:
opencv-samples-dev
libgles-omap3-x11demos
bc-cube-x11

Thanks,
Joel