OE-Core - What this means for Yocto/Poky and what we need to do
As most have gathered, there are changes afoot in the OE world and we
want to start increasing collaboration between Yocto and OE through the
creation of an OE-Core repository which both projects share.
This was going to be too much change for inclusion for the 1.0 release
but now that has branched we need to start working on this. I appreciate
that people have a number of different priorities but I'd ask that
people do read this email, take time to understand these changes and
bare with the inevitable disruption this change is going to cause.
Obviously we'll try and keep disruption to a minimum.
The implication for Yocto/Poky is that what is currently the meta
directory in the Poky repo is going to get split into two pieces. One
will be a mirror of the OE-Core repo (meta), the other will be yocto
specific pieces (meta-yocto). Each of these will be a layer.
For anything within the OE-Core directory, the patches need to be
submitted on the OE-Core mailing list. Patches to the other components
need to be separate and on the Poky list as things are today. I expect
the distro team to subscribe to the OE-Core list and participate there
on for discussions on core components:
meta-yocto patches and discussion should continue on the poky list as
I am prepared for now to help out getting user submitted patches for
Yocto/Poky, split up and submitted to OE-Core as needed. Ultimately, I'm
hoping we can enhance the tooling to understand layers and be able to
put send patches to the right places but we don't have such tools yet
and its a chicken and egg problem.
I also want to change the Poky repo so all the pieces contained within
are mirror copies of the appropriate upstreams. I've been working on
resolving the delta with upstream bitbake and for some components (docs,
meta-yocto, yocto-glue) we'll need to create them.
I'm going to start making these changes on the master branch as we're
under a lot of pressure from OE to start doing this *now*. I want to be
clear these changes are not destined for the 1.0 release.