public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/5 V2]support incremental deb image generation
Date: Mon, 4 Feb 2013 17:34:11 +0800	[thread overview]
Message-ID: <cover.1359968242.git.hongxu.jia@windriver.com> (raw)

Change from V1: fix do_rootfs error while using dash as default shell

The following is the test case about how to test incremental deb image
generation:

1, Modify a package 
1) Add the follow config option to a conf file:
    INC_DEB_IMAGE_GEN = "1"
    PACKAGE_CLASSES = "package_deb"

2) Run `bitbake core-image-sato' and test the image could work correctly.

3) Modify a package, such as busybox_1.20.2.bb.

4) Run `bitbake core-image-sato'

5) vim log.do_rootfs to see if the following log exists:
    `NOTE: Updating ***'

6) runqemu qemux86

2, Remove a package
1) Add the following line to conf/local.conf:
    INC_DEB_IMAGE_GEN = "1"
    PACKAGE_CLASSES = "package_deb"

2) Run "bitbake core-image-sato" to build an image

3) Comment out IMAGE_FEATURES in /meta/recipes-sato/images/core-image-sato.bb

4) Run "bitbake core-image-sato" to build an image

5) vim log.do_rootfs to see if the following log exists:
    `NOTE: Removing ***'

3, Add a package 
1) Add the following line to conf/local.conf:
    INC_DEB_IMAGE_GEN = "1"
    PACKAGE_CLASSES = "package_deb"
2) Do the above removing case.

3) Uncomment IMAGE_FEATURES in /meta/recipes-sato/images/core-image-sato.bb

4) Run `bitbake core-image-sato' to build an image

5) runqemu qemux86

The following changes since commit 75f470cd18d693a9a96d9849291c2c8de4dcbeb8:

  qt4: Add space for _appends (2013-02-01 22:49:47 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib hongxu/incremental-deb-image
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/incremental-deb-image

Hongxu Jia (5):
  apt-native:fix support configuring etc dir in apt.conf
  image.bbclass:support incremental deb image generation
  populate_sdk:support incremental deb image generation
  rootfs_deb.bbclass:support incremental deb image generation
  package_deb.bbclass:support incremental deb image generation

 meta/classes/image.bbclass                     |   37 ++-
 meta/classes/package_deb.bbclass               |  390 ++++++++++++++++++++++--
 meta/classes/populate_sdk_base.bbclass         |   13 +-
 meta/classes/populate_sdk_deb.bbclass          |    2 +-
 meta/classes/rootfs_deb.bbclass                |   58 +++-
 meta/recipes-devtools/apt/apt-native_0.7.14.bb |    2 +-
 meta/recipes-devtools/apt/files/apt.conf       |    2 +-
 7 files changed, 452 insertions(+), 52 deletions(-)

-- 
1.7.10.4




             reply	other threads:[~2013-02-04  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  9:34 Hongxu Jia [this message]
2013-02-04  9:34 ` [PATCH 1/5] apt-native:fix support configuring etc dir in apt.conf Hongxu Jia
2013-02-04  9:34 ` [PATCH 2/5] image.bbclass:support incremental deb image generation Hongxu Jia
2013-02-04  9:34 ` [PATCH 3/5] populate_sdk:support " Hongxu Jia
2013-02-04  9:34 ` [PATCH 4/5] rootfs_deb.bbclass:support " Hongxu Jia
2013-02-04  9:34 ` [PATCH 5/5] package_deb.bbclass:support " Hongxu Jia

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.1359968242.git.hongxu.jia@windriver.com \
    --to=hongxu.jia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox