From: William Mills <wmills@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: RFC: creating "extras" layer
Date: Tue, 12 Jun 2012 10:22:35 -0400 [thread overview]
Message-ID: <4FD750AB.9040700@ti.com> (raw)
In-Reply-To: <DD1A526D-B7EE-45D1-9DED-C2FB40897FBA@dominion.thruhere.net>
On 06/12/2012 09:44 AM, Koen Kooi wrote:
>
> Op 11 jun. 2012, om 20:17 heeft Denys Dmytriyenko het volgende geschreven:
>
>> Koen, et al,
>>
>> This is a RFC for creating an additional "extras" layer inside meta-ti to
>> contain pieces and components that are either slightly outdated (i.e. old
>> Davinci boards, hawk/crane etc.) or have best-effort status (TI81x, anything
>> DSP-related, etc.) or require non-standard dependencies besides OE-Core
>> (systemd?) with the possibility of moving them back to "main" meta-ti in the
>> future, once they become "first-class citizens", i.e. gain current and
>> continuing support.
>
> If it's going to be split this way I'd like to move all beagleboard.org related things out of meta-ti and into it's own seperate repo.
We should do whatever makes the most sense and serves all the user's
use-cases. Angstrom beagleboard is an important use case but so is
oe-core only on beagleboard and AM335x etc. We also need people to
understand what things are being built and tested every night vs
something that was pretty much working when it was tried 6 months ago.
> If the beagle recipes are demoted to 2nd class citizens we have no incentive anymore to be in meta-ti.
I thought it was just the older beagleboard stuff that was moving? Or
are you complaining that not every feature of your current builds are
available using just oe-core?
It is true that we are trying to do two things here:
1) separate things that require layers beyond oe-core
2) separate things that are not tested and supported to the same level
It was your assertion that we did not want too many layers.
Unfortunately that means things that require layers beyond oe-core need
to be in the second layer. Sorry if you see that as being a second
class citizen.
There are large parts of beagleboard and beaglebone that do work with
only oe-core and are built and tested regularly. Finding the right
place for these pieces should, I think, be the focus of the discussion.
As I have said before, If you want a seperate layer/repo to support the
specifics of Angstrom beagleboard/beaglebone _I_ think that would be fine.
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2012-06-12 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 1:17 RFC: creating "extras" layer Denys Dmytriyenko
2012-06-12 3:08 ` Maupin, Chase
2012-06-12 13:10 ` William Mills
2012-06-12 17:58 ` Denys Dmytriyenko
2012-06-12 13:44 ` Koen Kooi
2012-06-12 14:22 ` William Mills [this message]
2012-06-13 20:12 ` Koen Kooi
2012-06-12 16:46 ` Denys Dmytriyenko
2012-06-13 14:15 ` Enrico
2012-06-15 6:58 ` Steffen Sledz
2012-06-20 4:37 ` Jason Kridner
2012-06-20 6:59 ` Steffen Sledz
2012-06-20 14:11 ` Jason Kridner
2012-06-19 13:31 ` Thilo Fromm
2012-06-20 4:42 ` Jason Kridner
2012-06-20 7:12 ` Thilo Fromm
2012-06-20 14:09 ` Jason Kridner
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=4FD750AB.9040700@ti.com \
--to=wmills@ti.com \
--cc=koen@dominion.thruhere.net \
--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.