linux/poky.git/meta/classes/image.bbclass, branch 1.2_M4.rc1

gzip/pigz-native: Install into a prefix to avoid clashing with system binaries

2012-03-21T15:33:07+00:00

Due to the system providing a copy of gzip, we face some issues when we 'shadow' that copy with our own leading to a varient of race type bugs, and issues for example if a dependency such as libz is missing but the binary is still present. We usually rely on our dependency logic to protect us from this but for gzip, we don't have this protection since its not listed by all its users (and doing so would be impractical). This patch installed pigz and gzip into their own directory which we only add to PATH when we explictly want these binaries in much the same way we do with perl-native. This means dependency logic is correct when we use the binary and everything should work well. The patch adds an explict dependency into image.bbclass since the accelerated speed of compression is most appreciated at rootfs time. (From OE-Core rev: 7a98c0ef28822ae1fcee45b14db3edcfd4c7ad8f) Signed-off-by: Richard Purdie

classes/image: avoid cp race condition when building multiple images

2012-03-19T14:37:41+00:00

Avoid a race condition when building multiple images by ignoring a failure to copy the README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt to DEPLOY_DIR_IMAGE. (From OE-Core rev: 5a321f5840d4ed813e2a768871b33eff433d748c) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

image.bbclass: fix rootfs generation without package management tools

2012-03-13T11:45:08+00:00

When building without package management tools the ROOTFS_BOOTSTRAP_INSTALL packages need to be available to provide the bare minimal for rootfs unconfigure postinsts to be on first boot. Those packages where being include in core-image.bbclass' based images however every image needs those available for proper rootfs generation. (From OE-Core rev: 4f2845739fc7a1f2c784f4d3be048ee111e7d093) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

meta: Convert getVar/getVarFlag(xxx, 1) -> (xxx, True)

2012-03-05T18:22:56+00:00

Using "1" with getVar is bad coding style and "True" is preferred. This patch is a sed over the meta directory of the form: sed \ -e 's:\(\.getVar([^,()]*, \)1 *):\1True):g' \ -e 's:\(\.getVarFlag([^,()]*, [^,()]*, \)1 *):\1True):g' \ -i `grep -ril getVar *` Signed-off-by: Richard Purdie

image-vmdk: Create image_vmdk class and setup image and image_types to use it

2012-03-01T15:51:40+00:00

This creates a new image_vmdk class similar to live. The image_vmdk class needs to have a hddimg created by the image-live class, so it inherits it directly. The changes to image_types is to ensure that both live and vmdk images get the ext3 tools and dependencies. (From OE-Core rev: aa961e112b07d42c272e01f2d69f3c139e9ae70f) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

image.bbclass: do not create image manifest link if IMAGE_LINK_NAME is empty

2012-02-29T12:56:44+00:00

(From OE-Core rev: d0f1ae1f8cf8ef4e5adc24cc6246d3849e51aa98) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

image_types: Refactor compression code into a generic compression solution

2012-02-28T12:27:53+00:00

The current approach of adding each different compressed image type doesn't scale. This patch changes the code so compressed images for each form are automatically available using the form . in IMAGE_FSTYPES. This doesn't change any existing externally visible behaviour and the image generation process becomes more efficient as a result too. (From OE-Core rev: b7e4ed41ee480f00b7265341e9e2d2c2b9135143) Signed-off-by: Richard Purdie

More quoting fixes

2012-02-26T22:51:58+00:00

* We have various variables which are either not quoted at all or are half quoted. This patch fixes the bad exmaples so everything is consistent. (From OE-Core rev: 960ee8076e860353a05eb2eb7f825a455c54698d) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

image.bbclass: Ensure timestamp matches format used in initscripts after recent changes

2012-02-24T10:25:40+00:00

(From OE-Core rev: 173a48f79f8f2f18737f1901fc5992223d456348) Signed-off-by: Richard Purdie

Incremental rpm image generation

2012-01-11T10:36:22+00:00

Incremental rpm image generation, the rootfs would be totally removed and re-created in the second generation by default, but with INC_RPM_IMAGE_GEN = "1", the rpm based rootfs would be kept, and will do update(remove/add some pkgs) on it. NOTE: This is not suggested when you want to create a productive rootfs For example: 1) Add the follow config option to a conf file: INC_RPM_IMAGE_GEN = "1" 2) bitbake core-image-sato modify a package bitbake core-image-sato The rootfs would not be totally removed and re-created in the second generation, it would be simply updated based on the "package". Implatation: 1) Figure out the pkg which need to be removed or re-installed, then use 'rpm -e to remove the old one. Use the rpm's BUILDTIME to determine which pkg has been rebuilt. 2) Figure out the pkg which is newly added, and use 'rpm -U' to install it. This only for the rpm based rootfs, the deb and ipk based rootfs would be done later. [YOCTO #1651] (From OE-Core rev: 575ba3c9e153a1d8ac228a99a03ca2df5fbca151) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie