All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	Martin Jansa <martin.jansa@gmail.com>,
	Joe MacDonald <joe.macdonald@windriver.com>
Subject: Re: Proposal: Creating meta-networking
Date: Fri, 13 Jul 2012 17:15:33 +0100	[thread overview]
Message-ID: <4236628.uxsfNWTicv@helios> (raw)
In-Reply-To: <71A2669E-47B3-4F5F-B631-014BBB23CC9F@dominion.thruhere.net>

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.

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?

> 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,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-07-13 16:26 UTC|newest]

Thread overview: 23+ 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 ` Khem Raj
2012-06-15 15:42   ` [OE-core] " Khem Raj
2012-06-15 18:08   ` Otavio Salvador
2012-06-15 18:55     ` Andrei Gherzan
2012-06-15 19:55       ` Philip Balister
2012-06-16 17:10         ` Joe MacDonald
2012-06-16 17:36         ` Marko Lindqvist
2012-06-16 17:45           ` Otavio Salvador
     [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 [this message]
2012-07-16  7:16           ` Martin Jansa
2012-07-16 23:15       ` Paul Eggleton
2012-08-22 18:20 ` Christopher Larson
2012-08-22 18:59   ` Joe MacDonald
2012-08-22 19:22     ` Chris Larson
2012-08-22 19:37       ` Joe MacDonald
2012-08-22 19:41         ` Joe MacDonald
2012-08-23  6:22       ` Koen Kooi
2012-08-23 14:54         ` Joe MacDonald
  -- strict thread matches above, loose matches on Subject: below --
2012-07-23 12:57 Firago Alexey
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=4236628.uxsfNWTicv@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=joe.macdonald@windriver.com \
    --cc=koen@dominion.thruhere.net \
    --cc=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 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.