From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] core-image-sato.bb: increase free space size
Date: Wed, 3 Apr 2013 14:16:51 +0800 [thread overview]
Message-ID: <515BC953.2070504@windriver.com> (raw)
In-Reply-To: <515AAFDE.4020409@mlbassoc.com>
On 04/02/2013 06:15 PM, Gary Thomas wrote:
> On 2013-04-01 20:30, Qi.Chen@windriver.com wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Sato images, by default, have about 100M free space. This is not enough
>> and it blocks automatic testing.
>>
>> This patch fixes this problem by overriding the IMAGE_OVERHEAD_FACTOR
>> in the sato image recipe.
>>
>> [YOCTO #4109]
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> meta/recipes-sato/images/core-image-sato.bb | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/meta/recipes-sato/images/core-image-sato.bb
>> b/meta/recipes-sato/images/core-image-sato.bb
>> index e3246d2..8df1d08 100644
>> --- a/meta/recipes-sato/images/core-image-sato.bb
>> +++ b/meta/recipes-sato/images/core-image-sato.bb
>> @@ -9,3 +9,6 @@ LICENSE = "MIT"
>> inherit core-image
>>
>> IMAGE_INSTALL += "packagegroup-core-x11-sato-games"
>> +
>> +# Override IMAGE_OVERHEAD_FACTOR to increase the free space size on
>> sato images.
>> +IMAGE_OVERHEAD_FACTOR = "2.0"
>>
>
> You should make this overridable by the user:
> IMAGE_OVERHEAD_FACTOR ?= "2.0"
>
Yes. You're right.
And we can use "??=" in bitbake.conf.
A new patch set has been sent out.
Thanks,
Chen Qi
next prev parent reply other threads:[~2013-04-03 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 2:30 [PATCH 0/1] core-image-sato.bb: increase free space size Qi.Chen
2013-04-02 2:30 ` [PATCH 1/1] " Qi.Chen
2013-04-02 2:59 ` Khem Raj
2013-04-02 3:04 ` ChenQi
2013-04-02 10:15 ` Gary Thomas
2013-04-03 6:16 ` ChenQi [this message]
2013-04-03 10:38 ` Burton, Ross
2013-04-03 11:59 ` Otavio Salvador
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=515BC953.2070504@windriver.com \
--to=qi.chen@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.