From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Tobias Blom <tobias@blom.org>, openembedded-devel@lists.openembedded.org
Subject: Re: python-netifaces in oe?
Date: Mon, 24 Feb 2014 13:35:16 +0100 [thread overview]
Message-ID: <20140224123516.GD26981@jama> (raw)
In-Reply-To: <33174762.dysyrZqJd4@peggleto-mobl5.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
On Mon, Feb 24, 2014 at 12:19:07PM +0000, Paul Eggleton wrote:
> On Sunday 23 February 2014 22:26:34 Khem Raj wrote:
> > On Feb 23, 2014, at 10:23 PM, Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
> > wrote:
> > > We provide a recipe for python-netifaces in the meta-ros layer as well. In
> > > fact, a quick search on the OpenEmbedded Layer Index [1] reveals that
> > > meta-ros and meta-openstack both provide a recipe for python-netifaces.
> > > With your use case and recipe, we would have now three recipes. So, I
> > > suggest to unify all three recipes and come up with the best (complete)
> > > recipe from these three versions and add them to the meta-oe layer. We
> > > then can remove the duplicate recipes in the application layers.
> >
> > If these layers have dependency on meta-oe then please add the recipe there
> > and remove from other places.
>
> There has been some discussion about creating a meta-python layer (within the
> meta-openembedded repository) for these kinds of recipes. I think the time has
> come to actually do that, before we add any further python recipes to the
> general meta-oe layer. Could someone send a patch to create meta-python?
I don't mind accepting patch for creating meta-python layer, but the main reason
for it (python-numpy, python-nose, python-mako) were already merged into
oe-core before this question was answered :/
http://lists.openembedded.org/pipermail/openembedded-core/2014-January/088089.html
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-02-24 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94BAA6DD-BBE2-46CE-8248-E8432BE9F242@blom.org>
2014-02-20 14:43 ` python-netifaces in oe? Martin Jansa
2014-02-24 6:23 ` Lukas Bulwahn
2014-02-24 6:26 ` Khem Raj
2014-02-24 12:19 ` Paul Eggleton
2014-02-24 12:35 ` Martin Jansa [this message]
2014-02-24 13:10 ` Paul Eggleton
2014-02-24 17:41 ` Khem Raj
2014-02-24 17:43 ` Paul Eggleton
2014-02-24 18:42 ` Tobias Blom
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=20140224123516.GD26981@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=tobias@blom.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.