<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 29, 2013 at 4:57 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, 2013-08-29 at 12:49 +0100, Phil Blundell wrote:<br>
> On Thu, 2013-08-29 at 07:37 -0400, Robert P. J. Day wrote:<br>
> > distroless. i realize i *could* set a value for DISTRO, but it would<br>
> > seem that i shouldn't have to in order to avoid a build error.<br>
><br>
> Well, either you're using angstrom or you aren't. If you do want to use<br>
> it then you ought to set DISTRO appropriately, and if you don't want to<br>
> use it then you probably oughtn't to have the angstrom layer included at<br>
> all.<br>
><br>
> Trying to use the angstrom .bbappends and files with a different (or no)<br>
> distro configuration will give you a set of metadata that's neither one<br>
> thing nor the other and, even if you didn't get a build error, there's<br>
> no guarantee that the resulting image would actually work.<br>
<br>
</div>I'm not sure I agree. Ideally layers should be includable without<br>
turning on behaviour unless it is enabled. This is why we have things<br>
like an array of OVERRIDES to chose from.<br>
<br>
So I'd actually suggest this is a bug in the angstrom layer. There are<br>
also other layers which probably have issues, maybe including meta-yocto<br>
but we should fix them.<br>
<br>
I'll go further and suggest that Yocto Project Compatible status might<br>
depend on this in future (the current questions suggest it should be the<br>
case already).<br></blockquote></div><br>I agree wholeheartedly with this. Distro and BSP layers really need to be leveraging OVERRIDES for anything distro or machine specific.<br>-- <br>Christopher Larson</div></div>