is yocto based on oe-core *as-is*?

is yocto based on oe-core *as-is*?

[Robert P. J. Day]

  while i'm working my thru the docs, i want to verify that yocto is
built on top of oe-core straight from the oe-core repo, is that
correct?  as in, yocto doesn't make any yocto-specific mods to the
fundamental, lower-level OE core layers, does it?  it simply adds
layers on top, right?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: is yocto based on oe-core *as-is*?

[Paul Eggleton]

On Saturday 10 March 2012 04:40:15 Robert P. J. Day wrote:
>   while i'm working my thru the docs, i want to verify that yocto is
> built on top of oe-core straight from the oe-core repo, is that
> correct?  as in, yocto doesn't make any yocto-specific mods to the
> fundamental, lower-level OE core layers, does it?  it simply adds
> layers on top, right?

This is correct, and you can verify it by doing a diff of the OE-Core meta/ 
subdirectory against Poky's meta/ - the only difference is that Poky does not 
include the sample configs (it provides its own in meta-yocto).

It's also worth noting that Poky uses its own distro (policy) configuration via 
meta-yocto, although this builds upon the default policy in OE-Core.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: is yocto based on oe-core *as-is*?

[Gary Thomas]

On 2012-03-11 06:33, Paul Eggleton wrote:
> On Saturday 10 March 2012 04:40:15 Robert P. J. Day wrote:
>>    while i'm working my thru the docs, i want to verify that yocto is
>> built on top of oe-core straight from the oe-core repo, is that
>> correct?  as in, yocto doesn't make any yocto-specific mods to the
>> fundamental, lower-level OE core layers, does it?  it simply adds
>> layers on top, right?
>
> This is correct, and you can verify it by doing a diff of the OE-Core meta/
> subdirectory against Poky's meta/ - the only difference is that Poky does not
> include the sample configs (it provides its own in meta-yocto).

Have you actually done such a comparison?  I just compared them like this:
   poky/yocto:
      commit 320558f494c618f53e0c773db3ea0109476e8359
      Author: Paul Eggleton <paul.eggleton@linux.intel.com>
      Date:   Wed Feb 29 12:59:14 2012 +0000

   openembedded-core:
      commit 50dc8bfbac42b9a9b52a2f7d0568740c41790c13
      Author: Richard Purdie <richard.purdie@linuxfoundation.org>
      Date:   Fri Mar 9 14:14:04 2012 +0800

These are the up-to-date master branches, as of 2012-03-11 12:40 GMT

Tons of changes, many minor/cosmetic, but lots of substantial changes in
recipes, etc.  Maybe the Poky policy is to match oe-core (follow?), but at least
today, it's pretty far out of sync (10 days is forever in net-time)

>
> It's also worth noting that Poky uses its own distro (policy) configuration via
> meta-yocto, although this builds upon the default policy in OE-Core.
>
> Cheers,
> Paul
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: is yocto based on oe-core *as-is*?

[Paul Eggleton]

On Sunday 11 March 2012 06:46:17 Gary Thomas wrote:
> On 2012-03-11 06:33, Paul Eggleton wrote:
> > This is correct, and you can verify it by doing a diff of the OE-Core
> > meta/
> > subdirectory against Poky's meta/ - the only difference is that Poky does
> > not include the sample configs (it provides its own in meta-yocto).
> 
> Have you actually done such a comparison? 

Yes, I did so before sending the above message.

> I just compared them like this:
>    poky/yocto:
>       commit 320558f494c618f53e0c773db3ea0109476e8359
>       Author: Paul Eggleton <paul.eggleton@linux.intel.com>
>       Date:   Wed Feb 29 12:59:14 2012 +0000
> 
>    openembedded-core:
>       commit 50dc8bfbac42b9a9b52a2f7d0568740c41790c13
>       Author: Richard Purdie <richard.purdie@linuxfoundation.org>
>       Date:   Fri Mar 9 14:14:04 2012 +0800
> 
> These are the up-to-date master branches, as of 2012-03-11 12:40 GMT

I don't think you'll find they are. Your poky branch is behind OE-Core by quite 
a number of commits - in fact 320558f494c618f53e0c773db3ea0109476e8359 is 
where the 1.2_M3 branch HEAD is currently, are you sure you aren't on that 
branch instead of master?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: is yocto based on oe-core *as-is*?

[Gary Thomas]

On 2012-03-11 16:38, Paul Eggleton wrote:
> On Sunday 11 March 2012 06:46:17 Gary Thomas wrote:
>> On 2012-03-11 06:33, Paul Eggleton wrote:
>>> This is correct, and you can verify it by doing a diff of the OE-Core
>>> meta/
>>> subdirectory against Poky's meta/ - the only difference is that Poky does
>>> not include the sample configs (it provides its own in meta-yocto).
>>
>> Have you actually done such a comparison?
>
> Yes, I did so before sending the above message.
>
>> I just compared them like this:
>>     poky/yocto:
>>        commit 320558f494c618f53e0c773db3ea0109476e8359
>>        Author: Paul Eggleton<paul.eggleton@linux.intel.com>
>>        Date:   Wed Feb 29 12:59:14 2012 +0000
>>
>>     openembedded-core:
>>        commit 50dc8bfbac42b9a9b52a2f7d0568740c41790c13
>>        Author: Richard Purdie<richard.purdie@linuxfoundation.org>
>>        Date:   Fri Mar 9 14:14:04 2012 +0800
>>
>> These are the up-to-date master branches, as of 2012-03-11 12:40 GMT
>
> I don't think you'll find they are. Your poky branch is behind OE-Core by quite
> a number of commits - in fact 320558f494c618f53e0c773db3ea0109476e8359 is
> where the 1.2_M3 branch HEAD is currently, are you sure you aren't on that
> branch instead of master?

You're right, but I sure don't know how that happened!  I never have
anything but master checked out, but somehow this time I did.  Sorry
for the noise.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------