From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: OE-Classic recipe migration status
Date: Sun, 11 Nov 2012 19:58:09 +0000 [thread overview]
Message-ID: <2026428.K88ggMmWnu@helios> (raw)
In-Reply-To: <20121111195226.GA3407@jama.jama.net>
On Sunday 11 November 2012 20:52:26 Martin Jansa wrote:
> On Sun, Nov 11, 2012 at 07:11:28PM +0000, Paul Eggleton wrote:
> > Hi all,
> >
> > Whilst the OE-Core-based layer landscape has grown quite a bit over the
> > last year and we now have a wealth of clean and up-to-date recipes, I've
> > heard a few people commenting that we've still lost quite a few recipes
> > along the way. Nobody who did make that comment has seemed to be able to
> > be specific about what they thought we were missing however, so I figured
> > it would be worth trying to determine exactly which recipes are only
> > available in OE-Classic.
> >
> > With the help of some scripts I've produced a list of the recipes, made
> > some notes and categorised some of them. I've published the list on the
> > wiki (unfortunately I had to split it into two pages since it was too
> > large to put>
> > into one):
> > http://www.openembedded.org/wiki/OE-Classic_Recipes_A-I
> > http://www.openembedded.org/wiki/OE-Classic_Recipes_J-Z
> >
> > I don't know much about a lot of these recipes, so if you can help to fill
> > in the gaps particularly by marking the obsolete ones as such or adding
> > other comments, that would be great. Either edit the pages directly or
> > make your comments here and I'll merge them.
>
> I've noticed quite a few recipes listed here, which does exist in some
> layer (recipes mostly from meta-fso, meta-aurora, meta-shr), should I
> remove them from that wiki page or add layer name in 2nd column?
I did have all the layers in meta-smartphone included in the list I used to
filter this one, so if there are items that somehow didn't get removed I'd like
to figure out why. Can you list them here so I can look into that?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-11 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 19:11 OE-Classic recipe migration status Paul Eggleton
2012-11-11 19:52 ` Martin Jansa
2012-11-11 19:58 ` Paul Eggleton [this message]
[not found] ` <20121111201613.GB3407@jama.jama.net>
2012-11-11 20:49 ` Paul Eggleton
2012-11-11 23:24 ` [oe] " Otavio Salvador
2012-11-12 8:54 ` Paul Eggleton
2012-11-12 18:26 ` Stefan Schmidt
2012-11-19 13:57 ` Denis 'GNUtoo' Carikli
2012-11-12 22:10 ` Phil Blundell
2012-11-13 10:42 ` Paul Eggleton
2012-11-19 14:56 ` [oe] " Denis 'GNUtoo' Carikli
2012-11-19 15:03 ` Philip Balister
2012-11-19 17:15 ` Khem Raj
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=2026428.K88ggMmWnu@helios \
--to=paul.eggleton@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox