From: Denys Dmytriyenko <denys@ti.com>
To: "Kridner, Jason" <jdk@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Fix image recipes in meta-ti
Date: Sat, 1 Sep 2012 18:56:18 -0400 [thread overview]
Message-ID: <20120901225617.GF22219@edge> (raw)
In-Reply-To: <kkitbg3uuuda8t5puice0pub.1346534080222@email.android.com>
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@ti.com>
> To: "meta-ti@yoctoproject.org" <meta-ti@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.
next prev parent reply other threads:[~2012-09-01 22:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 21:07 Fix image recipes in meta-ti Cooper Jr., Franklin
2012-09-01 21:14 ` Kridner, Jason
2012-09-01 21:21 ` Cooper Jr., Franklin
2012-09-01 22:56 ` Denys Dmytriyenko [this message]
2012-09-02 16:16 ` Koen Kooi
2012-09-02 18:07 ` Cooper Jr., Franklin
2012-09-02 19:47 ` Maupin, Chase
2012-09-02 21:11 ` Koen Kooi
2012-09-04 13:53 ` Maupin, Chase
2012-09-13 23:16 ` Jason Kridner
2012-09-01 21:33 ` Maupin, Chase
2012-09-01 22:47 ` Denys Dmytriyenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120901225617.GF22219@edge \
--to=denys@ti.com \
--cc=jdk@ti.com \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.