From: Philip Balister <philip@balister.org>
To: Enrico <ebutera@users.berlios.de>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: RFC: 2 possible workarounds for recipes-misc dependency on Angstrom
Date: Mon, 17 Sep 2012 13:54:17 -0700 [thread overview]
Message-ID: <50578DF9.1030904@balister.org> (raw)
In-Reply-To: <CA+2YH7vzOwfqcfhM1xu8W=LmD-UV58zLQ6=XvokrCTh1AUvMnA@mail.gmail.com>
On 09/17/2012 01:36 PM, Enrico wrote:
> On Fri, Sep 14, 2012 at 10:06 PM, Maupin, Chase <chase.maupin@ti.com> wrote:
>> So really I think the question is do we have an agreement on "meta-beagle" or whatever it should be called, a timeline for it to be created and the recipes moved? Let's make meta-ti be the foundation BSP that we can all build on top of and nothing more or less.
>
> Sorry to jump into the discussion but...am i the only one that thinks
> that having meta-beagle, meta-panda, meta-whateverTIboard is crazy?
Whether or not Beagle is a TI board ....
It seems like the broader issue (and one I am falling over at the
moment) is that we want some image recipes in BSP's. The images have
different layer dependencies.
So we have a set of small images (such as board bring up and test
images) that depend only on oe-core, and more complex images that depend
on other layers. We can always mask the more complex images for the case
where we want to only build against oe-core, but this is not the most
convenient from a user point of view.
It seems like we need a way for an image to specify the layers it
requires and if those layers are not present, the recipe will not build,
but will not break parsing either.
Philip
>
> Enrico
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
next prev parent reply other threads:[~2012-09-17 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 6:43 RFC: 2 possible workarounds for recipes-misc dependency on Angstrom Denys Dmytriyenko
2012-09-14 6:46 ` [RFC: PATCH 1] ti-hw-bringup-image: fix 'no LICENSE' parsing error when meta-angstrom is not used Denys Dmytriyenko
2012-09-14 6:47 ` [RFC: PATCH 2] systemd-image: overlay local copy to enable building ti-hw-bringup-image Denys Dmytriyenko
2012-09-14 20:06 ` RFC: 2 possible workarounds for recipes-misc dependency on Angstrom Maupin, Chase
2012-09-17 20:36 ` Enrico
2012-09-17 20:42 ` Koen Kooi
2012-09-17 21:50 ` Denys Dmytriyenko
2012-09-17 23:27 ` Enrico
2012-09-17 20:54 ` Philip Balister [this message]
2012-09-17 21:47 ` Denys Dmytriyenko
2012-09-17 21:55 ` Denys Dmytriyenko
2012-09-18 0:16 ` Enrico
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=50578DF9.1030904@balister.org \
--to=philip@balister.org \
--cc=ebutera@users.berlios.de \
--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.