Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>,
	Joe MacDonald <joe.macdonald@windriver.com>
Subject: Re: Proposal: Creating meta-networking
Date: Mon, 16 Jul 2012 09:16:30 +0200	[thread overview]
Message-ID: <20120716071630.GA3729@jama.jama.net> (raw)
In-Reply-To: <4236628.uxsfNWTicv@helios>

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

On Fri, Jul 13, 2012 at 05:15:33PM +0100, Paul Eggleton wrote:
> On Friday 13 July 2012 18:03:08 Koen Kooi wrote:
> > Op 13 jul. 2012, om 17:58 heeft Paul Eggleton het volgende geschreven:
> > > On Thursday 12 July 2012 15:57:52 Joe MacDonald wrote:
> > >> Just to make sure we're got it in context, though, the open points were:
> > >>   - tcpdump listed in meta-oe's recipes-core/tasks/task-cli-tools,
> > >>   
> > >>     under RDEPENDS_${PN}-debug.
> > > 
> > > Koen, any suggestions? This task has pretty random contents - some of it
> > > is even hardware-specific. Do we really need to keep this together?
> > 
> > That's an SHR recipe, you'd have to ask Martin Jansa.
> 
> Ultimately we should not have anything distro-specific in meta-oe at all, which 
> means we all ought to have a say in its contents - otherwise it belongs in the 
> distro layer.

It was added from oe-core, because we (SHR) were still using it in our
images/tasks. If we're the only one user I don't mind moving it to our
distro layer or reworking it to something usefull for other people too.

> Martin, do you have any objection to this task recipe being reworked in the 
> face of the proposal to split tcpdump (and other networking-related recipes) 
> out to meta-networking?

Not at all.. I'll just add meta-networking to our layers setup..

> > The biggest blocker right now is where meta-networking is going to be
> > hosted, the layers in the meta-openembedded repo can only depend on oe-core
> > and bitbake, no other external layers.
> 
> I'll leave this for Joe to comment on.

Cheers,

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

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

  reply	other threads:[~2012-07-16  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 15:15 Proposal: Creating meta-networking Joe MacDonald
2012-06-15 15:42 ` [OE-core] " Khem Raj
     [not found] ` <1442756.zsKFTug4Rk@helios>
     [not found]   ` <20120712195752.GN3293@windriver.com>
     [not found]     ` <38351001.3KzA0t96MO@helios>
2012-07-13 16:03       ` Koen Kooi
2012-07-13 16:15         ` Paul Eggleton
2012-07-16  7:16           ` Martin Jansa [this message]
2012-07-16 23:15       ` Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2012-07-23 13:02 Firago Alexey
2012-07-24  0:09 ` Joe MacDonald

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=20120716071630.GA3729@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=joe.macdonald@windriver.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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