[OE-core] [RFC][PATCH 0/6] development vs. production builds

[Alexander Kanavin]

On 05/16/2017 04:47 PM, Patrick Ohly wrote:

> Then why is not already done like that in practice? Is it just because
> OE-core and Poky set such a bad precedence with teaching developers to
> add EXTRA_IMAGE_FEATURES ?= "debug-tweaks" to make the images usable,
> and then that approach gets copied?

It is done like that already, it's just not very consistent from what I 
can see. For example, core-image-sato-dev.bb:
=============
require core-image-sato.bb

DESCRIPTION = "Image with Sato for development work. It includes 
everything \
within core-image-sato plus a native toolchain, application development 
and \
testing libraries, profiling and debug symbols."

IMAGE_FEATURES += "dev-pkgs"
=============

> I think everyone agrees that removing "debug-tweaks" would be a good
> idea. But completely removing the global (sic!) EXTRA_IMAGE_FEATURES in
> local.conf.sample would go even further, and I am not sure how the
> reactions to that would be. I suspect there are people who find it
> useful to have just one image recipe that gets build in different
> configurations (dangerous and not so dangerous).

I'm not sure either, but I think that's not actually a bad idea - 
dropping support for it altogether. :)

I'm not a big fan of placing INHERIT into local.conf either, by the way. 
I believe in functional programming principles, and this goes directly 
against them.

Alex