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

[Burton, Ross]

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

On 1 December 2017 at 19:45, Andre McCurdy <armccurdy at gmail.com> wrote:

> 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
> >>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20171204/24fc5a6b/attachment-0002.html>