[meta-ti] Fix image recipes in meta-ti

[Denys Dmytriyenko]

On Sat, Sep 01, 2012 at 09:14:43PM +0000, Kridner, Jason wrote:
> Will meta-oe take the recipes?

Well, those maybe better suited for meta-angstrom instead... If you think 
about it - cloud9 is an important component of default Beaglebone images based 
on Angstrom, so images with the cloud9 in the name are naturally associated 
with Angstrom. Anybody else who'd like to use meta-ti as BSP layer outside of 
Angstrom would most probably use own images anyway...

-- 
Denys


> -------- Original message --------
> Subject: [meta-ti] Fix image recipes in meta-ti
> From: "Cooper Jr., Franklin" <fcooper at ti.com>
> To: "meta-ti at yoctoproject.org" <meta-ti at yoctoproject.org>
> CC:
> 
> 
> When debugging issues in meta-arago I frequently try building recipes using  
> the meta-ti,meta-oe and oe-core layers. However, I always have to remove the 
> following recipes due to ?This recipe does not have the LICENSE field set? 
> error:
> cloud9-gfx-image.bb
> cloud9-gnome-image.bb
> cloud9-image.bb
> 
> The issue is these recipes have an include from meta-angstrom that provides 
> this LICENSE field. Meta-ti should not have this dependency so these recipes 
> should be fixed to address this. I personally do not think cloud9 related 
> recipes that install  cloud9, nodejs, mplayer etc.. should even be in 
> meta-ti which is a BSP layer but that is a completely different discussion. 
> I also don?t believe pulling in the include file that is needed from 
> meta-angstrom is also a reasonably solution. Either these recipes need to be 
> fixed so that they can work in meta-ti with only a dependency on meta-oe and 
> oe-core. Or remove the recipes from this layer and pull it into 
> meta-angstrom which I believe is the best option.