From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: OE-Classic recipe migration status
Date: Tue, 13 Nov 2012 10:42:02 +0000 [thread overview]
Message-ID: <1509472.8pSTkUQEym@helios> (raw)
In-Reply-To: <1352758235.6869.152.camel@x121e.pbcl.net>
On Monday 12 November 2012 22:10:35 Phil Blundell wrote:
> On Sun, 2012-11-11 at 19:11 +0000, Paul Eggleton wrote:
> > 136 PERL
>
> I encountered the horror that is the perl modules a few weeks ago while
> I was working on mythtv. At the time it seemed as though there were
> more like 13600 recipes but I imagine your figure is probably the
> accurate one. It looks as though I managed to fix up 37 recipes to work
> with oe-core before the tedium got too much.
I'm only counting recipes with "perl" in the name, there could be others but I
suspect that has caught most of them.
> I think this stuff probably wants to go into a dedicated
> meta-perl-modules layer since in most cases there is no obvious
> functional grouping.
Sounds good.
> I could publish those 37 as a starting point and
> anybody else who wants to add more is welcome to do so.
Great, thanks!
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-13 10:55 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
[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 [this message]
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=1509472.8pSTkUQEym@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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