Patchwork [2/2] core-image-sato.bb: increase free space size

login
register
mail settings
Submitter Qi.Chen@windriver.com
Date April 3, 2013, 6:16 a.m.
Message ID <3d56b617bac180023326d302a14d675710d4380d.1364969701.git.Qi.Chen@windriver.com>
Download mbox | patch
Permalink /patch/47321/
State New
Headers show

Comments

Qi.Chen@windriver.com - April 3, 2013, 6:16 a.m.
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 setting the default value of
IMAGE_OVERHEAD_FACTOR to "2.0" in the sato image recipe.

[YOCTO #4109]

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
 meta/recipes-sato/images/core-image-sato.bb |    4 ++++
 1 file changed, 4 insertions(+)
Saul Wold - April 3, 2013, 3:28 p.m.
On 04/02/2013 11:16 PM, 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 setting the default value of
> IMAGE_OVERHEAD_FACTOR to "2.0" in the sato image recipe.
>
We need to think hard about this one, we have a couple of conflicting 
interests here with the amount of space.

The Poky distro and core-image-sato are examples of for the community 
and developers to use, we want to set good examples where ever possible. 
One of the intentions of core-image-sato is to show a compact image with 
a graphical user interface, so having a minimal, but usable amount of 
free space is important. We don't want someone new to look at this and 
see a large image as it might put them off the project without 
understanding the tune-ability. This is an embedded environment, not a 
desktop with a large disk, we want to share that message.

Another goal of the Poky distro is to create something that is testable 
and automated testing is important part of this.  I read the bug report 
and commented on it as well.  Is there a way to clean-up after the 
tests?  Are single tests consuming the 100M available? Is it slowly 
accumulating tmp space?

What other options can we do here?  Do we need to consider a different 
image for testing?  Or build 2 images similarly one with extra space?

We need to think about the different scenarios and usage.

Thanks
	Sau!


> [YOCTO #4109]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>   meta/recipes-sato/images/core-image-sato.bb |    4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/images/core-image-sato.bb
> index e3246d2..4b4e595 100644
> --- a/meta/recipes-sato/images/core-image-sato.bb
> +++ b/meta/recipes-sato/images/core-image-sato.bb
> @@ -9,3 +9,7 @@ LICENSE = "MIT"
>   inherit core-image
>
>   IMAGE_INSTALL += "packagegroup-core-x11-sato-games"
> +
> +# Increase the default value of IMAGE_OVERHEAD_FACTOR from "1.3" to "2.0"
> +# to increase the free space size in sato images.
> +IMAGE_OVERHEAD_FACTOR ?= "2.0"
>

Patch

diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/images/core-image-sato.bb
index e3246d2..4b4e595 100644
--- a/meta/recipes-sato/images/core-image-sato.bb
+++ b/meta/recipes-sato/images/core-image-sato.bb
@@ -9,3 +9,7 @@  LICENSE = "MIT"
 inherit core-image
 
 IMAGE_INSTALL += "packagegroup-core-x11-sato-games"
+
+# Increase the default value of IMAGE_OVERHEAD_FACTOR from "1.3" to "2.0"
+# to increase the free space size in sato images.
+IMAGE_OVERHEAD_FACTOR ?= "2.0"