From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core@lists.openembedded.org
Subject: Re: OE TSC Minutes 4 June 2013
Date: Sat, 08 Jun 2013 12:43:33 +0100 [thread overview]
Message-ID: <1562117.pR91UQbp4e@helios> (raw)
In-Reply-To: <20130607222052.GN22710@jama>
On Saturday 08 June 2013 00:20:52 Martin Jansa wrote:
> > a. oe-classic recipe migration status
> > drop from agenda after this
>
> Not sure why I got this idea now when it's "over" but would it be
> possible to populate new layerindex with at least recipe names from
> OE-classic?
>
> I guess it would be hard to parse it completely as proper layer,
> but it would be nice to search for "foo" and see that it's available in
> OE-classic ready to be migrated to some layer - otherwise people will
> just start from scratch which isn't always best way.
>
> Even just names from migration wiki page would be enough to give people
> heads-up that something similar is in OE-classic.
Indeed, I had thought of this... I think we could do a one-off hacked up parse
to get the data into a separate table and then it would be more or less
static. At least it would give us an easy way to report on recipes that
haven't been migrated (currently I've been doing it with some scripts).
FYI I've been doing some work in my spare time on the layer index code
recently, implementing additional features and tidying a few things up
(published in the paule/features branch). The barrier to getting this up on
the live site is further testing and the database migration which I haven't
been through yet other than locally; I guess the less migrations the better so
it would probably be worth implementing the OE-Classic data structures before
that happens. I'll take a look at this if I have some spare time over the next
couple of weeks.
Cheers,
Paul
next prev parent reply other threads:[~2013-06-08 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 21:54 OE TSC Minutes 4 June 2013 Jeff Osier-Mixon
2013-06-07 22:20 ` Martin Jansa
2013-06-07 22:30 ` Jeff Osier-Mixon
2013-06-08 11:43 ` Paul Eggleton [this message]
2013-06-07 22:50 ` Philip Balister
2013-06-07 22:59 ` Jeff Osier-Mixon
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=1562117.pR91UQbp4e@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