From: Denys Dmytriyenko <denis@denix.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: RFC: creating "extras" layer
Date: Tue, 12 Jun 2012 12:46:53 -0400 [thread overview]
Message-ID: <20120612164653.GA32573@denix.org> (raw)
In-Reply-To: <DD1A526D-B7EE-45D1-9DED-C2FB40897FBA@dominion.thruhere.net>
On Tue, Jun 12, 2012 at 08:44:59AM -0500, 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. If the beagle
> recipes are demoted to 2nd class citizens we have no incentive anymore to be
> in meta-ti.
Disclaimer: no beagles were harmed in the making of this film...
Seriously though, none of the beagle recipes (requiring systemd or not) were
moved yet for several reasons:
1. As done with some other recipes, it's possible to have systemd services w/o
inheriting systemd.bbclass, i.e. do it manually - I was planning on looking
into this option in the near future.
2. There was a recent discussion about systemd work being started in OE-Core
and it was confirmed on today's call that the new Intel team in Romania is
gearing up to integrate systemd into OE-Core in the very near future.
3. And, of course, a separate systemd layer in meta-oe might help, if done
properly and allowing easily target both systemd and sysvinit from the same
recipe...
Anyway, it is not my intention to demote beagle support to 2nd class citizens.
After all, beagles are the most supported platforms in meta-ti right now and a
very good example for other platforms to follow...
I hope you are not just looking for any excuse to move out of meta-ti - we
just need to work on a better positioning of meta-ti...
--
Denys
next prev parent reply other threads:[~2012-06-12 16:47 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
2012-06-13 20:12 ` Koen Kooi
2012-06-12 16:46 ` Denys Dmytriyenko [this message]
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=20120612164653.GA32573@denix.org \
--to=denis@denix.org \
--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.