On 02/24/2016 06:47 PM, Martin Jansa wrote:
Many people aren't using poky and don't want to play with combo-layer or format-patch/am combo to reapply the patches from poky repo to oe-core repo. As you're definitely used to such strange environment, can you please push corresponding branch for oe-core to openembedded-core-contrib repo as well? Thanks!
>
I should start reading the cover letters :), will remove this from master-next until openembedded-core-contrib branch is available.
I think you misunderstood my intent somewhat. I don't want you to queue these patches anywhere, they are preliminary. Their purpose is twofold:
1) People interested in playing and testing that poky branch with introspection may want to use recipes or whole layers from meta-oe as well (gupnp for instance).
2) I'd like to demonstrate to you that meta-oe will be taken care of when introspection lands in oe-core, because historically there's been some bad blood regarding those disruptive oe-core changes :)
However, I'm reluctant to provide the patchset for oe-contrib. The reason is that I've been maintaining the poky patchset since November; it's more or less rebasing, merge conflicts fixing and world rebuilding once every one or two weeks. I wouldn't want to duplicate this ongoing work for oe-contrib as well, and keep the two branches in sync, because I don't actually know when these patches make it to master. So if you want to try them out against pure oe-core, you have to extract and apply them by hand, I'm afraid. As a one-off task, it should not be complicated.
Alex -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
