[OE-core] [PATCH] bitbake.conf: set more conservative default for IMAGE_FSTYPES_DEBUGFS

[Andre McCurdy]

On Tue, Nov 7, 2017 at 2:35 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
> On Fri, Oct 27, 2017 at 2:50 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
>> 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).
>
> Ping.

Ping again. Any issues with this change?

>> Signed-off-by: Andre McCurdy <armccurdy at gmail.com>
>> ---
>>  meta/conf/bitbake.conf | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
>> index 9696273..15feb57 100644
>> --- 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.
>> --
>> 1.9.1
>>