From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: OE-Classic recipe migration status
Date: Sun, 11 Nov 2012 19:11:28 +0000 [thread overview]
Message-ID: <12301427.Yf0uchSh3U@helios> (raw)
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.
Using some more hacky scripts to break down the recipes into groups, I've
produced the following numbers (with the incomplete data as it stands):
1484 other
218 BSP
211 BugLabs
195 libs
193 obsolete
155 obsolete directory (OE-Classic)
136 PERL
119 python
92 distro
89 tasks
84 nonworking directory (OE-Classic)
80 GPE
79 X11 drivers
59 images
59 games
41 fonts
23 security
20 in another layer
18 pending
11 EFL
So clearly there are quite a few recipes left that could be brought back,
assuming there is demand; on the other hand there are a significant number that
can probably just be discarded. For those that are still of interest, we need
motivated individuals to do the migration and maintain the recipes going
forward.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2012-11-11 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 19:11 Paul Eggleton [this message]
2012-11-11 19:52 ` OE-Classic recipe migration status Martin Jansa
2012-11-11 19:58 ` Paul Eggleton
[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=12301427.Yf0uchSh3U@helios \
--to=paul.eggleton@linux.intel.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