[yocto] yocto beagleboard.conf -- should it not go away?

[Richard Purdie]

On Tue, 2012-09-04 at 09:21 +0100, Jack Mitchell wrote:
> On 03/09/12 22:08, Bruce Ashfield wrote:
> > On Mon, Sep 3, 2012 at 4:55 PM, Tomas Frydrych
> > <tf+lists.yocto at r-finger.com> wrote:
> >> snip...
> >>
> >>
> >>
> >> That being said, taking a step back, what are you trying to get out of
> >> meta-yocto in this scenario ? oe-core + meta-ti is probably what you
> >> should be using.
> >>
> 
> Sorry to jump in here, but this is actually a very interesting point. 
>  From coming to OpenEmbedded through Yocto and subsequently learning 
> about the ecosystem as a whole, I have always considered meta-yocto to 
> be providing a sane distro configuration. This implies that I believe 
> the oe-core default distro configuration, even though it will build, the 
> result won't be very satisfying - or maybe a bit disjointed.
>
> You seem to be saying above that the meta-yocto layer is only any good 
> for providing the kernel framework, and as he is not using the framework 
> (i.e. using meta-ti) then there is no point in using the meta-yocto 
> layer? So does the Poky distro config only really slap a name on the 
> oe-core default distro policy - or does it have some added value?

In the old days, there was no default distro config. OE-Core changed
that as an experiment which IMO has been relatively successful. The Poky
distro config inherits as much as possible from the core defaults. The
extras are (reading poky.conf):

* Example of Distro Branding
* Ensuring some particular kernel versions
* Particular SDK layout
* Minor tweaks to basic images/qemu images
* Mirror Setup (although OE-Core has these now too iirc)
* Sets connectivity check
* Sets list of compatible/tested distros
* Some signature stuff (now OE-Core default)
* Sets more stringent package sanity checks that OE-Core

So at least some of the above moved into the core as default although we
still need to remove the remnants from the poky.conf file. Others will
likely move in future too.

There isn't anything major above but there are several smaller usability
tweaks/optimisations and I'd argue there is some added value.

There are also example LSB and "tiny" profiles showing how to take the
system and customise it in different ways which I'd argue have value
too.

> I'm not trying to rile anyone up here, just trying to put the jigsaw 
> together as the picture looks different every time I revisit it!!

Its an evolving picture, hopefully in a good way :)

Cheers,

Richard