meta-yocto preppends itself to BBPATH; seemingly there is a long standing convention in OE that layers should append to the BBPATH, and it seems to be followed by most layers (including oe-core and meta-intel). Breaking this convention makes it difficult to include meta-yocto with other layers, such as BSP layers, because no layer that follows this convention can override config files contained in meta-yocto. For example, if meta-yocto and meta-ti are included in a project, the beagleboard.conf that is part of meta-yocto will always be used regardless of the order in which the layers are included. In the absence of any other provision for prioritization of conf files than the ordering of the BBPATH, it is fairly essential that a convention of some sort is followed and meta-yocto seems to be the odd one out here. Fixing this requires only a small change in the layer.conf and the Yocto bblayers sample file (plus regeneration of bblayers at the user end). I would be nice if this could be fixed for the 1.4 release.
Timely as I'm in the middle of some patches which should fix this problem although not the way you're expecting ;-)
Excellent, and if fixed in a more robust way than having a 'convention', even better. :)
Fixed in: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2000698b17011bbde1c3e5bb01a7d6763316db5a You can now select the meta-yocto-bsp and meta-yocto distro policy layers separately. The BSP layer now appends to BBPATH so should resolve this issue. I think its reasonable for the distro policy to prepend which it continues to do so.