[oe] [meta-networking][PATCH] openflow: Add latest from git

[Laszlo Papp]

On Wed, Sep 4, 2013 at 2:13 PM, Philip Balister <philip at balister.org> wrote:

> <snip>
> > The same applies to anyone else working on a layer with clearly
> > networking components that may be reluctant to incorporate it into
> > meta-net.  I'm welcoming submissions of useful components and I'd be
> > really disappointed if we ended up having the same (or similar)
> > recipes in multiple public layers purely due to reticence and
> > (perceived?) extra dependencies.  I'll be other meta-oe maintainers
> > feel the same, too.  Balkanisation benefits no one.
> >
> > Back on topic, then.
>
> I am really late to the game ...
>
> If you are having trouble figuring out what layer a recipe belongs in
> due to it being needed for several layers, maybe the package in question
> belongs in oe-core.


You are not just late, but also quite off IMHO ... ;-)

As written already, and if you had taken the time to look into the software
in question, you would have realized that from more than one point of view
that this standard is definitely a domain specific network material. It is
*far* away from being a core component.

Off-topic: I do not understand why meta-virtualization is this messy. That
seems to cause the whole annoyance in here on top of the "give me the
credit for a few lines which can only be written in one way" other
argument. Anyway, this seems to be an appropriate trigger for
meta-virtualization to get some stabilization. Past mistakes are no excuse
for introducing more, in my book.