[meta-ti] RFC: creating "extras" layer

Denys Dmytriyenko denis at denix.org
Tue Jun 12 09:46:53 PDT 2012


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



More information about the meta-ti mailing list