Re: [yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

2017-10-23 Thread Burton, Ross
On 23 October 2017 at 12:39, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > poky is generated using combo-layer, which effectively cherry-picks > commits from the parent repositories (in this case bitbake, > > oe-core, meta-poky, meta-yocto-bsp). This explains why the SHAs don't

Re: [yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

2017-10-23 Thread Zoran Stojsavljevic
> poky is generated using combo-layer, which effectively cherry-picks commits from the parent repositories (in this case bitbake, > oe-core, meta-poky, meta-yocto-bsp). This explains why the SHAs don't match, as the history doesn't match. This is exactly my original point. We should have here

[yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

2017-10-23 Thread Zoran Stojsavljevic
> Or better yet use > http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-ma nual.html#ref-classes-image-buildinfo Since I am also (relatively) new to YOCTO, reading these emails makes me think about dependencies between YOCTO distros and layers within distros. Looking what is written here,