From: William Mills <wmills@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 1/3] matrix-gui-browser: port from arago overlay
Date: Fri, 27 Jan 2012 15:34:58 -0500 [thread overview]
Message-ID: <4F230A72.5090609@ti.com> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1010BF9D92A@DLEE12.ent.ti.com>
On 01/27/2012 03:29 PM, Maupin, Chase wrote:
>> On 01/27/2012 03:21 PM, Denys Dmytriyenko wrote:
>> How about splitting meta-ti into:
>>> * BSP only
>>> * SGX graphics
>>> * DSP tools
>>> * WiFi etc.
>>>
>>> And then splitting meta-arago into:
>>> * Arago distro for TI SDKs
>>> * Supplemental apps
>>>
>> Need to get my "YES!" in here before everyone barfs all over the
>> proposal :)
> I'm good with this. I was also planning in meta-arago to at least put all bbappends in a recipes-appends directory so it was easy to track the things we are "tweaking" vs. the recipes. Arago today is too much of a mix between amends and recipes in my opinion. I would even say that Tom's proposal (from IRC) of splitting the arago distro and supplemental apps into two layers would be a good idea so that other distros can pull our supplemental apps if they want pretty easily. And that way we don’t keep adding more repos to manage.
Yes, this is what I was talking about all along. Sorry if I was not clear.
next prev parent reply other threads:[~2012-01-27 20:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 18:46 [PATCH 1/3] matrix-gui-browser: port from arago overlay Chase Maupin
2012-01-26 18:46 ` [PATCH 2/3] refresh-screen: add package from arago Chase Maupin
2012-01-26 18:46 ` [PATCH 3/3] matrix-gui: update to latest version Chase Maupin
2012-01-26 22:44 ` [PATCH 1/3] matrix-gui-browser: port from arago overlay William Mills
2012-01-27 11:50 ` Koen Kooi
2012-01-27 12:09 ` Andreas Müller
2012-01-27 12:24 ` Koen Kooi
2012-01-27 17:38 ` William Mills
2012-01-27 19:39 ` Denys Dmytriyenko
2012-01-27 19:47 ` Koen Kooi
2012-01-27 20:09 ` Denys Dmytriyenko
2012-01-27 13:50 ` Maupin, Chase
2012-01-27 14:54 ` Philip Balister
2012-01-27 15:19 ` Maupin, Chase
2012-01-27 17:51 ` William Mills
2012-01-27 19:46 ` Maupin, Chase
2012-01-27 20:03 ` William Mills
2012-01-27 20:05 ` William Mills
2012-01-27 20:10 ` Tom Rini
2012-01-27 20:11 ` Denys Dmytriyenko
2012-01-27 20:19 ` Philip Balister
2012-01-27 20:24 ` Denys Dmytriyenko
2012-01-27 20:20 ` William Mills
2012-01-27 20:11 ` William Mills
2012-01-27 20:17 ` Maupin, Chase
2012-01-27 20:21 ` Denys Dmytriyenko
2012-01-27 20:24 ` William Mills
2012-01-27 20:29 ` Maupin, Chase
2012-01-27 20:34 ` Denys Dmytriyenko
2012-01-27 20:39 ` Maupin, Chase
2012-01-27 20:42 ` William Mills
2012-01-27 20:44 ` Maupin, Chase
2012-01-27 20:48 ` William Mills
2012-01-27 20:34 ` William Mills [this message]
2012-01-27 20:50 ` Philip Balister
2012-01-27 20:54 ` Koen Kooi
2012-01-27 20:57 ` Denys Dmytriyenko
2012-01-27 22:40 ` Philip Balister
2012-01-27 23:39 ` Denys Dmytriyenko
2012-01-27 20:53 ` Koen Kooi
2012-01-27 20:55 ` Maupin, Chase
2012-01-27 21:52 ` William Mills
2012-01-27 23:04 ` Koen Kooi
2012-01-28 3:23 ` Philip Balister
2012-01-27 17:30 ` William Mills
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=4F230A72.5090609@ti.com \
--to=wmills@ti.com \
--cc=chase.maupin@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.