[OE-core] [PATCH] meta/conf/layer.conf: Add recommended download layer

[Mark Hatle]

On 11/23/16 7:16 PM, Christopher Larson wrote:
> On Wed, Nov 23, 2016 at 12:42 PM, Mark Hatle <mark.hatle at windriver.com
> <mailto:mark.hatle at windriver.com>> wrote:
> 
>     On 11/23/16 12:56 PM, Martin Jansa wrote:
>     > On Wed, Nov 23, 2016 at 12:38:42PM -0600, Mark Hatle wrote:
>     >> On 11/23/16 12:10 PM, Martin Jansa wrote:
>     >>> On Wed, Nov 23, 2016 at 11:42:09AM -0600, Mark Hatle wrote:
>     >>>> This is a Wind River specific patch and not generally applicable.
>     >>>
>     >>> Then why is it sent to oe-core ML?
>     >>
>     >> As noted in the cover letter, I'm required to by Yocto Project compliance
>     >> requirements.
>     >>
>     >> As indicated LAST time I got scolded, I was told to indicate this in the patch
>     >> summary email -- which I did.
>     >
>     > Sorry I've noticed the cover letter only after the response.
>     >
>     > So it's only because of this requirement from Yocto Project compliance?
> 
>     yes.
> 
>     > "Have all patches applied to BitBake and OpenEmbedded-Core (if present)
>     > been submitted to the open source community?"
>     >
>     > Shouldn't the wording be change to something like "all applicable
>     > patches" or "all generally useful patches"?
>     >
>     > It seems strange to send project specific patches together with cover
>     > saying that they aren't generally applicable and shouldn't be merged,
>     > just because of this requirement.
> 
>     It was done this way to prevent people from cheating and claiming something was
>     (effectively) not useful/applicable/etc when it some special secret sauce.
> 
>     Even these patches while not generally applicable could give someone else the
>     idea to duplicate (or improve) on our approach at providing layer specific
>     download layers.
> 
> 
> More of an implementation question, but presumably you could have your setup
> scripts add the LAYERRECOMMENDS to bblayers.conf, rather than having it in your
> oe-core fork/branch, as an alternative.

The recommends need to be indexed by the layer index program.  The layer index
program processes one layer at a time, and there is no way to inject things.

I can manually add dependencies, however the next time I create a branch -- I
have to do this again... and again... and again....   For our product we need to
have the layer.conf setup properly so that the layer index will index the
dependencies (including the recommended layers.)

--Mark

> -- 
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics