From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] Incremental image generation(Add config sample)
Date: Thu, 29 Dec 2011 09:33:29 -0800 [thread overview]
Message-ID: <4EFCA469.8020607@linux.intel.com> (raw)
In-Reply-To: <b77e4e9e630e0ae691e6f524c356745e0c42ffb2.1325141432.git.liezhi.yang@windriver.com>
On 12/28/2011 11:00 PM, Robert Yang wrote:
> Add the config sample for incremental image generation to
> meta-yocto/conf/local.conf.sample
>
> [YOCTO #1651]
>
> Signed-off-by: Robert Yang<liezhi.yang@windriver.com>
> ---
> meta-yocto/conf/local.conf.sample | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/meta-yocto/conf/local.conf.sample b/meta-yocto/conf/local.conf.sample
> index ca8636c..e33ffd9 100644
> --- a/meta-yocto/conf/local.conf.sample
> +++ b/meta-yocto/conf/local.conf.sample
> @@ -222,3 +222,10 @@ PATCHRESOLVE = "noop"
> # track the version of this file when it was generated. This can safely be ignored if
> # this doesn't mean anything to you.
> CONF_VERSION = "1"
> +
> +# Incremental image generation(only for rpm based rootfs currently), the rootfs
> +# would be totally removed and re-created in the second generation by default,
> +# but with INC_IMAGE_GEN = "1", the 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
> +#INC_IMAGE_GEN = "1"
This should probably belong in the local.conf.sample.extended file.
Sau!
next prev parent reply other threads:[~2011-12-29 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 7:00 [PATCH 0/2] Incremental image generation(rpm based rootfs) Robert Yang
2011-12-29 7:00 ` [PATCH 1/2] " 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 [this message]
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=4EFCA469.8020607@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