All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.linuxtogo.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: OE-Classic recipe migration status
Date: Sun, 11 Nov 2012 20:49:56 +0000	[thread overview]
Message-ID: <4701269.Boc8pSq2zM@helios> (raw)
In-Reply-To: <20121111201613.GB3407@jama.jama.net>

On Sunday 11 November 2012 21:16:13 Martin Jansa wrote:
> On Sun, Nov 11, 2012 at 07:58:09PM +0000, Paul Eggleton wrote:
> > On Sunday 11 November 2012 20:52:26 Martin Jansa wrote:
> > > 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?
>
> Ah sorry, you're probably right
> 
> 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/0298befc97dc5dca2
> a3721fb0ff9d4caf8d24f84
> 
> So I'll just update [distro] flag to something like obsoleted by
> libfsoframework.

Ah ok, sounds good.

> 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.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.linuxtogo.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] OE-Classic recipe migration status
Date: Sun, 11 Nov 2012 20:49:56 +0000	[thread overview]
Message-ID: <4701269.Boc8pSq2zM@helios> (raw)
In-Reply-To: <20121111201613.GB3407@jama.jama.net>

On Sunday 11 November 2012 21:16:13 Martin Jansa wrote:
> On Sun, Nov 11, 2012 at 07:58:09PM +0000, Paul Eggleton wrote:
> > On Sunday 11 November 2012 20:52:26 Martin Jansa wrote:
> > > 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?
>
> Ah sorry, you're probably right
> 
> 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/0298befc97dc5dca2
> a3721fb0ff9d4caf8d24f84
> 
> So I'll just update [distro] flag to something like obsoleted by
> libfsoframework.

Ah ok, sounds good.

> 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.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2012-11-11 21:04 UTC|newest]

Thread overview: 27+ 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:52   ` [OE-core] " Martin Jansa
2012-11-11 19:58   ` Paul Eggleton
2012-11-11 19:58     ` [OE-core] " Paul Eggleton
     [not found]     ` <20121111201613.GB3407@jama.jama.net>
2012-11-11 20:49       ` Paul Eggleton [this message]
2012-11-11 20:49         ` Paul Eggleton
2012-11-11 23:24         ` [oe] " Otavio Salvador
2012-11-11 23:24           ` [OE-core] " Otavio Salvador
2012-11-12  8:54           ` [oe] " Paul Eggleton
2012-11-12  8:54             ` [OE-core] " Paul Eggleton
2012-11-12 18:26 ` Stefan Schmidt
2012-11-12 18:26   ` [OE-core] " Stefan Schmidt
2012-11-13 10:52   ` Paul Eggleton
2012-11-17  8:49     ` Martin Jansa
2012-11-19 13:57   ` Denis 'GNUtoo' Carikli
2012-11-19 13:57     ` [OE-core] " 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 14:56   ` Denis 'GNUtoo' Carikli
2012-11-19 15:03   ` [oe] " Philip Balister
2012-11-19 15:03     ` Philip Balister
2012-11-20 23:48   ` [OE-core] " Paul Eggleton
2012-11-19 17:15 ` Khem Raj
2012-11-19 17:15   ` [OE-core] " Khem Raj
2012-11-20 23:50   ` Paul Eggleton

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=4701269.Boc8pSq2zM@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.linuxtogo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.