Increase free space size on sato images

From: Chen Qi <[email protected]>

The following changes since commit fd4e5c6c58183f1a017c6b5fe4d43c320e273567:

meta-yocto/conf: Add conf-notes.txt (2013-04-02 23:13:21 +0100)

are available in the git repository at:

git://git.pokylinux.org/poky-contrib ChenQi/sato-size
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/sato-size

Chen Qi (2):
bitbake.conf: use weaker assignment for IMAGE_OVERHEAD_FACTOR core-image-sato.bb: increase free space size

 meta/conf/bitbake.conf                      |    2 +-
 meta/recipes-sato/images/core-image-sato.bb |    4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

1.7.9.5

From: Chen Qi <[email protected]>

This allows image recipes to set a default value and still provides an option for users to override it.

For example, we set a default value in core-image-sato.bb.

    IMAGE_OVERHEAD_FACTOR ?= "2.0"

And users who build sato image could still override it in their distro conf files or local.conf.

[YOCTO #4109]

---
 meta/conf/bitbake.conf |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

index cd5d61e..6d947d8 100644
@@ -412,7 +412,7 @@ IMAGE_LINK_NAME = "${IMAGE_BASENAME}-${MACHINE}"
 
 # This option allows for a percentage overage of the actual image size rather than a
 # fixed extra space, this is space needed for initial startup and basic operations.
-IMAGE_OVERHEAD_FACTOR ?= "1.3"
+IMAGE_OVERHEAD_FACTOR ??= "1.3"
 # This option allows for adding additional space in K above and beyond what the 
 # IMAGE_OVERHEAD_FACTOR might add. This space is for additional packages, user data, ...
 # To set a fixed size then overriding IMAGE_ROOTFS_SIZE with the max size one wants

1.7.9.5

From: Chen Qi <[email protected]>

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]

---
 meta/recipes-sato/images/core-image-sato.bb |    4 ++++
 1 file changed, 4 insertions(+)

index e3246d2..4b4e595 100644
@@ -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"

1.7.9.5

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!