Re: [PATCH 1/3] matrix-gui-browser: port from arago overlay

[William Mills <wmills@ti.com>]

On 01/27/2012 07:24 AM, Koen Kooi wrote:
>
> Op 27 jan. 2012, om 13:09 heeft Andreas Müller het volgende geschreven:
>
>> On Fri, Jan 27, 2012 at 12:50 PM, Koen Kooi<koen@dominion.thruhere.net>  wrote:
>>> Since meta-arago is supposed to be as empty as possible and matrix doesn't play well with others it's a bad fit for both meta-arago and meta-oe. Maybe we should split the meta-ti repo into 2 layers: one for BSP things (including sgx, dsp, etc) and one for 'sdk' things (matrix).
>>> The idea is to keep reusable TI deliverables together without forcing people to use arago. Putting matrix in meta-arago would mean you can only use it with DISTRO=arago, which is a huge step backwards from the current situation.
>>>
>> I think splitting out BSP into an own layer is a good idea and sorry
>> for another hijacking: This would be a good chance to make it
>> independent of angstrom ( e.g ti-hw-bringup ).
>
> Image reuse is the least of the issues, SOC_FAMILY is a much larger one.
>

Andreas: Yes, this is the layer stack independence that meta-ti is 
suppose to have and currently does not.  When meta-ti is "done" it is 
suppose to work in:

core layer stack: oe-core + meta-ti
yocto layer stack: poky + meta-ti
angstrom layer stack: oe-core + meta-oe + meta-angstrom + meta-ti + many 
more)
arago layer stack: TBD but at least oe-core + meta-oe + meta-ti + 
meta-arago)

As Koen points out we have a good many hurdles to get to the above. 
Stay tuned.