2.4.2.2. Build History Image Information

+2.4.2.2. Build History Image Information

+ The files produced for each image are as follows: +

build-id: + Human-readable information about the build configuration + and metadata source revisions.
*.dot: + Dependency graphs for the image that are + compatible with graphviz. +
files-in-image.txt: + A list of files in the image with permissions, + owner, group, size, and symlink information. +
image-info.txt: + A text file containing name-value pairs with information + about the image. + See the following listing example for more information. +
installed-package-names.txt: + A list of installed packages by name only.
installed-package-sizes.txt: + A list of installed packages ordered by size. +
installed-packages.txt: + A list of installed packages with fuill package + filenames.

Note

+ Installed package information is able to be gathered and + produced even if package management is disabled for the final + image. +

+ Here is an example of image-info.txt: +

+     DISTRO = poky
+     DISTRO_VERSION = 1.1+snapshot-20120207
+     USER_CLASSES = image-mklibs image-prelink
+     IMAGE_CLASSES = image_types
+     IMAGE_FEATURES = debug-tweaks x11-base apps-x11-core \
+        package-management ssh-server-dropbear package-management
+     IMAGE_LINGUAS = en-us en-gb
+     IMAGE_INSTALL = task-core-boot task-base-extended
+     BAD_RECOMMENDATIONS = 
+     ROOTFS_POSTPROCESS_COMMAND = buildhistory_get_image_installed ;   rootfs_update_timestamp ;  
+     IMAGE_POSTPROCESS_COMMAND = buildhistory_get_imageinfo ; 
+     IMAGESIZE = 171816
+

+ Other than IMAGESIZE, which is the + total size of the files in the image in Kbytes, the + name-value pairs are variables that may have influenced the + content of the image. + This information is often useful when you are trying to determine + why a change in the package or file listings has occurred. +