[Openembedded-architecture] bblayers.conf - Past, Present and Future?

[Koen Kooi]

> Op 11 mei 2016, om 10:44 heeft Richard Purdie <richard.purdie at linuxfoundation.org> het volgende geschreven:
> 
> On Wed, 2016-05-11 at 11:08 -0300, Otavio Salvador wrote:
>> On Wed, May 11, 2016 at 8:42 AM, Richard Purdie
>> <richard.purdie at linuxfoundation.org> wrote:
>> ...
>>> In parallel, we're seeing people trying to use OE in CI systems. To
>>> make buildbot work for the Yocto Project, we have a ton of
>>> configuration and "fetching" code and I know Jenkins integration
>>> runs
>>> into the same issues. We'd love to be able to throw away the need
>>> to
>>> have CI specific layer addition code, or the bulk of the custom git
>>> fetcher we ended up having to add there for example.
>> 
>> We have a script which hides most of this for us. The OSYIS[1] help
>> us
>> to hide this.
>> 
>> 1. http://code.ossystems.com.br/gitweb?p=osyis.git
>> 
>> For Jenkins we just fetch the code (which it has nice plugins for
>> repo) and use the OSYIS to setup the build for us. It has support for
>> modules which allow for custom handles to be written when need.
>> 
>> I think adding a setup logic on BitBake violates the KISS principle.
> 
> Keep in mind that its exactly for that reason I don't want to have
> bitbake itself actually fetching layers and I'm proposing a separate
> tool.
> 
> I am proposing it be in the bitbake repository so that its easily
> available and encourages some kind of standardisation.
> 
> Right now, everyone does this differently and we have the same problem
> YP was trying to set out and solve in a different area, "Multiple ways
> of doing kind of the same thing, differently, each with advantages but
> also with some disadvantages”.

I know this suggestion is being-part-of-the-problem-instead-of-the-solution, but what about having 2 ‘reference’ distros side by side on yocto-project.org instead of just poky? Poky can show what combo-layer can give you and the other can show a different setup. 

I originally floated the idea to break away from the yocto==poky monoculture and resulting confusion, but it could serve other purposes if we can’t agree on using a single tool as base for bblayers.conf/fetching.

regards,

Koen