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).

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 9696273acc0f0a5da15197d3c1ac5b970f6e06b4..15feb573db09c8dbd2b725f61e4005f233f368f3 100644 (file)
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -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.