Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 2/2] meta-python: move recipes from meta-oe
Date: Thu, 17 Jul 2014 16:40:38 +0200	[thread overview]
Message-ID: <20140717144038.GL2433@jama> (raw)
In-Reply-To: <1546726.9iZKeAkyu0@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]

On Thu, Jul 17, 2014 at 03:20:51PM +0100, Paul Eggleton wrote:
> On Thursday 17 July 2014 07:07:01 Tim Orling wrote:
> > Well, that's embarrassing. Thank you, Martin. Obviously, I forgot to push a
> > local commit. I guess I'd better move to the back of the bus!
> > 
> > 
> > On Wed, Jul 16, 2014 at 5:50 AM, Martin Jansa <martin.jansa@gmail.com>
> > wrote:
> > > On Tue, Jul 15, 2014 at 04:32:34PM -0700, Tim Orling wrote:
> > > >      * Move recipes from meta-openembedded/meta-oe that are not
> > > >      
> > > >        depended upon by recipes already in meta-oe (e.g. gateone,
> > > >        anki)
> > > >      
> > > >      * Recipes NOT moved:
> > > >        python-futures
> > > >        python-pyopenssl
> > > >        python-simplejson
> > > >        python-tornado
> > > >        python-pyqt
> > > >        python-sip
> > > > 
> > > > Signed-off-by: Tim Orling <TicoTimo@gmail.com>
> > > > ---
> > > > 
> > > >  .../recipes-devtools/python => meta-python/recipes-python}/pyrtm_0.2.bb
> 
> I just noticed, this doesn't fit the normal pattern of 
> recipes-xyz/something/*.bb - there's a missing directory level. It's entirely 
> cosmetic, but if we do want to fix it we ought to do so now.

I've fixed it already (in master-next) and it's not just cosmetic,
because without the directory it's not included in BBFILES pattern.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-07-17 14:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 23:32 [meta-oe][PATCH 0/2] meta-python creation Tim Orling
2014-07-15 23:32 ` [meta-oe][PATCH 1/2] meta-python: create layer Tim Orling
2014-07-15 23:32 ` [meta-oe][PATCH 2/2] meta-python: move recipes from meta-oe Tim Orling
2014-07-16 12:38   ` Martin Jansa
2014-07-16 12:50   ` Martin Jansa
2014-07-17 14:07     ` Tim Orling
2014-07-17 14:20       ` Paul Eggleton
2014-07-17 14:40         ` Martin Jansa [this message]
2014-07-18 15:47           ` Paul Eggleton
2014-07-22 19:01 ` [meta-oe][PATCH 0/2] meta-python creation Martin Jansa
2014-07-23  1:03   ` Stephen Arnold
2014-07-23  8:00     ` Martin Jansa

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=20140717144038.GL2433@jama \
    --to=martin.jansa@gmail.com \
    --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