From: Robert Yang <liezhi.yang@windriver.com>
To: <mark.hatle@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Incremental image generation(rpm based rootfs)
Date: Thu, 29 Dec 2011 15:00:11 +0800 [thread overview]
Message-ID: <cover.1325141432.git.liezhi.yang@windriver.com> (raw)
Testing:
1) Enable INC_IMAGE_GEN = "1" in conf/local.conf
2) $ bitbake core-image-sato
* Test when remove some pkgs
a) Save the modify time of file which is in
tmp/work/qemux86_64-poky-linux/core-image-sato-1.0-r0/rootfs/dev/.
b) Edit meta/recipes-sato/images/core-image-sato.bb, remove
${SATO_IMAGE_FEATURES} from IMAGE_FEATURES.
c) bitbake core-image-sato
Result: The project built well, check the modify time of the file
which is in
tmp/work/qemux86_64-poky-linux/core-image-sato-1.0-r0/rootfs/dev/,
They should be the same to step a)'s, which means that these files
were note newly created.
* Testh when add some pkgs
a) Save the modify time of file which is in
tmp/work/qemux86_64-poky-linux/core-image-sato-1.0-r0/rootfs/dev/.
b) Edit meta/recipes-sato/images/core-image-sato.bb, add the
${SATO_IMAGE_FEATURES} back to IMAGE_FEATURES.
c) bitbake core-image-sato
Result: The project built well, check the modify time of the file
which is in
tmp/work/qemux86_64-poky-linux/core-image-sato-1.0-r0/rootfs/dev/,
They should be the same to step a)'s, which means that these files
were note newly created.
* Test when edit a pkg
a) bitbake bzip2 -cclean
b) rm -f rm -f sstate-cache/sstate-bzip2-*
c) Edit meta/recipes-extended/bzip2/bzip2_1.0.6.bb
d) bitbake core-image-sato
Result: The project built well, and check:
tmp/work/qemux86-poky-linux/core-image-sato-1.0-r0/temp/log.do_rootfs
Only the bzip2 has been re-installed
// Robert
The following changes since commit f5aa3bbda623c8fae3a761d72fddc95631ad0706:
coreutils: ensure --color works so DEPEND on libcap (2011-12-24 10:05:47 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/inc_image_gen
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/inc_image_gen
Robert Yang (2):
Incremental image generation(rpm based rootfs)
Incremental image generation(Add config sample)
meta-yocto/conf/local.conf.sample | 7 ++++
meta/classes/image.bbclass | 11 +++++-
meta/classes/package_rpm.bbclass | 72 +++++++++++++++++++++++++++++++-----
3 files changed, 78 insertions(+), 12 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-12-29 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 7:00 Robert Yang [this message]
2011-12-29 7:00 ` [PATCH 1/2] Incremental image generation(rpm based rootfs) Robert Yang
2011-12-29 7:00 ` [PATCH 2/2] Incremental image generation(Add config sample) Robert Yang
2011-12-29 17:33 ` Saul Wold
2011-12-30 1:21 ` Robert Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1325141432.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.