From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.linuxtogo.org,
Martin Jansa <martin.jansa@gmail.com>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [oe] OE-Classic recipe migration status
Date: Mon, 12 Nov 2012 08:54:03 +0000 [thread overview]
Message-ID: <5245949.8fOfhN9Jo3@helios> (raw)
In-Reply-To: <CAP9ODKoiaAJzAZEcH0doQkNZSXuqaOzM0_rsopLCswR-uHOOAA@mail.gmail.com>
On Sunday 11 November 2012 21:24:55 Otavio Salvador wrote:
> On Sun, Nov 11, 2012 at 6:49 PM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
> > On Sunday 11 November 2012 21:16:13 Martin Jansa wrote:
> > > I've noticed e.g this:
> > > libfsobasics [distro]
> > > libfsoresource [distro]
> > > libfsosystem [distro]
> > > libfsotransport [distro]
> > > but those are now provided by single libfsoframework recipe and I've
> > > forgot this change
> >
> > https://github.com/shr-distribution/meta-smartphone/commit/0298befc97dc5dc
> > a2>
> > > a3721fb0ff9d4caf8d24f84
> > >
> > > So I'll just update [distro] flag to something like obsoleted by
> > > libfsoframework.
> >
> > Ah ok, sounds good.
FYI I've updated these entries now.
> > > The rest is probably also not 1:1 like qfsodbusxml2cpp-native
> > > ./meta-fso/recipes-freesmartphone/freesmartphone/qfsodbusxml2cpp_git.bb
> > >
> > > Maybe you can try to update scripts to show matches after "-native"
> > > suffix strip?
> >
> > I'd prefer to handle this manually - there are cases when newer recipes
> > haven't been BBCLASSEXTENDed to handle -native so I've been checking this
> > by hand.
>
> You might grep for it and match it properly. So it drops a manual step.
OK, I've added some script code to check for BBCLASSEXTEND and have added
notes next to the following items that I had missed:
cup-native
devio-native
jamvm-native
jlex-native
python-pygobject-native
qfsodbusxml2cpp-native
usbpath-native
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-12 9:09 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 [this message]
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=5245949.8fOfhN9Jo3@helios \
--to=paul.eggleton@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.linuxtogo.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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