[yocto-ab] Angstrom Request for Yocto Project Compatibility Status

[William Mills]

On 09/04/2012 12:36 PM, Richard Purdie wrote:
> This raises some questions and may highlight a grey area in the
> compliance questions.
>
> Angstrom is requesting compliance with our 1.2 release. Its lists the
> meta-oe layer as a dependency in its README (for the wrong reasons but
> Koen fixed that when prompted).
>
> The key question is:
>
> """
> Are hardware support, configuration (distro) policy, and recipe metadata
> separated into different layers which do not depend on each other?
> """
>
> and this clearly and very publicly wasn't the case for the denzil (1.2)
> branch of meta-oe.

meta-oe is actually a number of layers.  I presume you have verified 
that the mixing occurs in layers that Angstrom actually uses, correct?

Is meta-yocto actually clean in regard to this rule??

>
> Angstrom requires meta-oe to build and hence one of its components is in
> clear violation of the above question. So my recommendation is to say
> that Angstrom isn't compatible with 1.2 but likely will be for 1.3 and
> suggest they reapply then.

Koen could also rework the 1.2 branch of meta-oe.  He is not limited to 
what meta-oe looked like at the point YP 1.2 was released.  I don't 
think there is any time criteria in the compliance statements.

>
> I'd note that meta-oe master has made changes to separate out the policy
> elements into a separate layer which would remove the obstacle faced for
> 1.2.
>
> The grey area is whether the above question applies to the layer *and*
> all components it requires as listed in the README or not. It makes no
> sense for this not to be the case but I know people like to interpret
> these things literally so we may want to consider clarifying this.
>
> Any strong opinions on this? Should we clarify the question or wait to
> "rev" the specification and include something then?
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab