bitbake.conf: set more conservative default for IMAGE_FSTYPES_DEBUGFS
PATCH 1/1 bitbake.conf: set more conservative default for IMAGE_FSTYPES_DEBUGFS
Setting IMAGE_FSTYPES_DEBUGFS to the same value as IMAGE_FSTYPES can lead to creating a large number of DEBUGFS filesystem images, many of which may not make much sense (or may not even be buildable).
--- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/bitbake.conf +1 -1
@@ -757,7 +757,7 @@ require conf/sanity.conf DL_DIR ?= "${TOPDIR}/downloads" SSTATE_DIR ?= "${TOPDIR}/sstate-cache" IMAGE_FSTYPES ?= "tar.gz" -IMAGE_FSTYPES_DEBUGFS ?= "${IMAGE_FSTYPES}" +IMAGE_FSTYPES_DEBUGFS ?= "tar.gz" INITRAMFS_FSTYPES ?= "cpio.gz" # The maximum size in Kbytes for the generated initramfs image size.
Signature · 1 line
1.9.1
Quoted 3 lines · Andre McCurdy
Setting
IMAGE_FSTYPES_DEBUGFSto the same value asIMAGE_FSTYPEScan lead to creating a large number of DEBUGFS filesystem images, many of which may not make much sense (or may not even be buildable).
Ping.
Quoted 21 lines
Signed-off-by Andre McCurdy <[email protected]>--- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/conf/bitbake.conf +1
-2@@ -757,7 +757,7 @@ require conf/sanity.conf DL_DIR ?= "${TOPDIR}/downloads" SSTATE_DIR ?= "${TOPDIR}/sstate-cache" IMAGE_FSTYPES ?= "tar.gz" -IMAGE_FSTYPES_DEBUGFS ?= "${IMAGE_FSTYPES}" +IMAGE_FSTYPES_DEBUGFS ?= "tar.gz" INITRAMFS_FSTYPES ?= "cpio.gz" # The maximum size in Kbytes for the generated initramfs image size. --1.9.1
Quoted 6 lines · Andre McCurdy
Quoted 3 lines · Andre McCurdy
Setting
IMAGE_FSTYPES_DEBUGFSto the same value asIMAGE_FSTYPEScan lead to creating a large number of DEBUGFS filesystem images, many of which may not make much sense (or may not even be buildable).Ping.
Ping again. Any issues with this change?
Quoted 21 lines
Quoted 21 lines
Signed-off-by Andre McCurdy <[email protected]>--- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/conf/bitbake.conf +1
-2@@ -757,7 +757,7 @@ require conf/sanity.conf DL_DIR ?= "${TOPDIR}/downloads" SSTATE_DIR ?= "${TOPDIR}/sstate-cache" IMAGE_FSTYPES ?= "tar.gz" -IMAGE_FSTYPES_DEBUGFS ?= "${IMAGE_FSTYPES}" +IMAGE_FSTYPES_DEBUGFS ?= "tar.gz" INITRAMFS_FSTYPES ?= "cpio.gz" # The maximum size in Kbytes for the generated initramfs image size. --1.9.1
Nope its queued now. You'll have noticed from the status reports we've been holding back on merging whilst trying to stabilise the autobuilders.
Ross
Quoted 38 lines · Andre McCurdy
Quoted 1 line · Andre McCurdy
On Fri, Oct 27, 2017 at 2:50 PM, Andre McCurdy <[email protected]>
Quoted 5 lines · wrote:
Quoted 3 lines
Setting
IMAGE_FSTYPES_DEBUGFSto the same value asIMAGE_FSTYPEScan lead to creating a large number of DEBUGFS filesystem images, many of which may not make much sense (or may not even be buildable).Ping.
Ping again. Any issues with this change?
Quoted 16 lines
Quoted 16 lines
Signed-off-by Andre McCurdy <[email protected]>--- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/conf/bitbake.conf +1
-1@@ -757,7 +757,7 @@ require conf/sanity.conf DL_DIR ?= "${TOPDIR}/downloads" SSTATE_DIR ?= "${TOPDIR}/sstate-cache" IMAGE_FSTYPES ?= "tar.gz" -IMAGE_FSTYPES_DEBUGFS ?= "${IMAGE_FSTYPES}" +IMAGE_FSTYPES_DEBUGFS ?= "tar.gz"Quoted 5 lines
Quoted 5 lines
meta/conf/bitbake.conf +0
-1INITRAMFS_FSTYPES ?= "cpio.gz" # The maximum size in Kbytes for the generated initramfs image size. --1.9.1
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core