[OE-core] GUI based images

[Khem Raj]

On Tue, May 9, 2017 at 1:39 PM, Alexander Kanavin
<alexander.kanavin at linux.intel.com> wrote:
> On 05/09/2017 11:19 PM, Khem Raj wrote:
>>
>> I think we should always intend to align the reference stack with
>> whats commonly used in
>> userbases we target to address with project, we will not be serving
>> the project goals and its username if we
>> trim down to packages which are just used for reference, if majority of
>> the
>> community we intend to address uses QT or any other stack for that matter
>> then we should align our requirements accordingly which will be mutually
>> beneficial IMO
>
>
> I strongly disagree. Oe-core is not a Greatest Embedded Hits collection or
> any kind of 'reference stack', and decisions on what goes into it should not
> be based on how popular it is. If you do this, you risk overextending the
> layer, and ending up not doing a particularly good job on any of the things
> it tries to do. It's best to allow other layers to flourish, let the domain
> specialists do their job and decide for themselves how they want to do
> things, and have a curated list of layers that are known to be high quality
> and approved by Yocto Project.
>
> If you want qt5, use meta-qt5 and meta-b2qt, both made by people who
> actually develop the Qt stack itself. End of story.

Don't get bogged down with QT5, its not at all about QT5 or no qt5,see
it from a users point of view and you will probably understand what I
am trying to say. Relevance of what you include in core is very
essential. Look at
any infra typical example is android, they ensure what consists of the core
pieces and keep them aligned and add/remove major pieces with newer
releases. We need to always evaluate coverage of core and make amends
if we dont then integration efforts become more over releases and at
some point a distro can decide its not worth using OE-Core and fork.
So evaluating
the sub-systems should always be done and we should not be afraid of
shuffling the cards if that aligns well with what the users are needing at
a certain point in time.