From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2 ] V3 Incremental rpm image generation
Date: Wed, 11 Jan 2012 22:42:51 -0800 [thread overview]
Message-ID: <4F0E80EB.8060503@linux.intel.com> (raw)
In-Reply-To: <cover.1326191431.git.liezhi.yang@windriver.com>
On 01/10/2012 02:38 AM, Robert Yang wrote:
> Changes of V3:
> * Change the name from INC_RPM_IMAGE_GEN to INC_RPM_IMAGE_GEN as Richard
> suggested, and it will only work for rpm based rootfs, the deb and ipk
> will be done in M3.
>
> * Update rootfs_rpm.bbclass since other developer has modified it since
> V2.
>
> Changes of V2:
> * Move the config sample from meta-yocto/conf/local.conf.sample to
> meta-yocto/conf/local.conf.sample.extended as Saul suggested.
>
> Testing:
> 1) Add INC_RPM_IMAGE_GEN = "1" to 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
>
>
>
> The following changes since commit 468998cddbe1a803096c9b357e1b5daa3b7e8c2e:
>
> command.py: add parseConfigurationFiles API (2012-01-06 16:01:44 +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 rpm image generation
> Incremental rpm image generation(Add config sample)
>
> meta-yocto/conf/local.conf.sample.extended | 7 +++
> meta/classes/image.bbclass | 11 ++++-
> meta/classes/package_rpm.bbclass | 73 ++++++++++++++++++++++++----
> meta/classes/rootfs_rpm.bbclass | 6 ++-
> 4 files changed, 84 insertions(+), 13 deletions(-)
>
Merged into OE-Core
'
Thanks
Sau!
prev parent reply other threads:[~2012-01-12 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 10:38 [PATCH 0/2 ] V3 Incremental rpm image generation Robert Yang
2012-01-10 10:38 ` [PATCH 1/2 " Robert Yang
2012-01-10 10:38 ` [PATCH 2/2 ] V3 Incremental rpm image generation(Add config sample) Robert Yang
2012-01-12 6:42 ` Saul Wold [this message]
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=4F0E80EB.8060503@linux.intel.com \
--to=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox