[meta-ti] question on meta-ti for yocto

[William Mills]

>> Op 21 mrt. 2012, om 23:10 heeft Richard Purdie het volgende geschreven:
>>> The trouble is Koen keeps doing this and nobody in general replies. The
>>> lack of a reply can be seen as to condone what was said and its
>>> certainly leading to people getting more confused. I think a response
>>> was appropriate.

For the record I will try to speak for the official TI position on this.
-------------------

1) Koen speaks for himself.  He does not speak for TI.  He is not a TI 
employee any longer but he remains a valuable contributor to 
beagleboard, angstrom, oe-core, meta-oe, and meta-ti among many others. 
  I think we all benefit from his [ code :) ] contributions.

2) When people ask about building for "yocto" we (TI) assume they mean 
building using the poky component of yocto.

3) Angstrom is a valuable member of the openembedded eco system and 
enables much progress in oe-core and other areas.  Angstrom is based on 
oe-core, as is poky.  Angstrom is not an official yocto project. 
Therefore TI believes that when people are building based on Angstrom, 
they are NOT building "yocto".

4) Denys, Koen, and others are working to ensure that meta-ti can be 
used with just oe-core or just poky.

5) meta-ti will be able to be used in an Angstrom configuration but 
(now) does not, and will not, require it.

6) Although we plan to support base oe-core and poky configurations, 
they will *not* be recommended configurations for several reasons:
6.1) oe-core and poky ignore ~ 12 month of toolchain improvements made 
by Linaro.
6.2) At this time, all of the internal and customer validation of TI 
BSPs has been done with a gcc 4.5 based toolchain that includes the 
linaro patches.

As stated in #6, TI will continue to recommend meta-oe in the layer 
stack to get the toolchain that TI tests with.  We hope, as work with 
linaro continues to switch that to an official meta-linaro layer.

TI will continue to test with and recommend a toolchain that is closely 
aligned with Linaro.  We see no reason customers should have to misalign 
themselves with the ARM ecosystem just to align with poky.

---------------------------------
[speaking for myself now]

I fully support base poky testing but I think we are getting dangerously 
close to a defacto statement that the only real yocto based distro is 
one that _only_ uses poky + a BSP layer.  I am not aligned with that 
view.  I think oe-core and poky are a fine base but many customers will 
need to expand on what is there with more layers.

Richard,

You seem to take offense at Koen's claim that Angstrom is Yocto.  As I 
stated above I don't think Angstrom _is_ yocto but how do we refer to 
distributions that are based off of oe-core or even poky that include 
other layers.  Are they "Yocto based" or "Yocto aligned"?  How about 
"Yocto adjacent" :) ?

Koen,

The next time someone asks how to build "yocto" can you let Denys answer 
please :)

Thanks,
Bill