Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Firago Alexey <Alexey_Firago@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Proposal: Creating meta-networking
Date: Mon, 23 Jul 2012 17:02:15 +0400	[thread overview]
Message-ID: <500D4B57.3020800@mentor.com> (raw)

Hi all,

On 6/15/2012 8:15 AM, Joe MacDonald wrote:
> We've been talking about this on-and-off at Wind River for a while now,
> but it now seems like a reasonable time to bring a proposal to the OE
> community at large.  We're thinking about creating a new layer to house
> recipes, etc.  for networking packages.
> ...
> So what does everyone think?  Awesome idea?  Terrible idea?  (Hopefully)
> something in between?  All feedback is welcome.

I think creating software support layer for network related packages is 
good idea.
We've updated some of the recipes from OE Classic mentioned above for 
our projects at Mentor Graphics.
We've been thinking to place these updated recipes in meta-oe layer. But 
I think now that separate layer like meta-networking
would be much more suitable place.  Also we've created some new packages 
like mipv6-umip or multipath-tools
that are good candidates for being placed in meta-networking.

So, I suggest Mentor Graphics would contribute to meta-networking.

--
Alexey Firago**|Software Engineer, Embedded Systems Division, Mentor 
Graphics


             reply	other threads:[~2012-07-23 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 13:02 Firago Alexey [this message]
2012-07-24  0:09 ` Proposal: Creating meta-networking Joe MacDonald
  -- strict thread matches above, loose matches on Subject: below --
2012-06-15 15:15 Joe MacDonald
     [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
2012-07-16 23:15       ` 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=500D4B57.3020800@mentor.com \
    --to=alexey_firago@mentor.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