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

[Laszlo Papp]

I still do not follow why you are not waiting patiently for an update. I
have already written that I would send one soon (this thread demoralized me
and "motivated" though for a bit of delay).

All the discussion would have been spared in here, as the issues were
addressed before I even sent the wrong version.

How about reviewing other pending changes for weeks like stunnel?


On Thu, Sep 5, 2013 at 2:04 PM, Joe MacDonald <joe at deserted.net> wrote:

> [Re: [oe] [meta-networking][PATCH] openflow: Add latest from git] On
> 13.09.05 (Thu 10:01) Burton, Ross wrote:
>
> > On 5 September 2013 05:39, Bruce Ashfield <bruce.ashfield at gmail.com>
> wrote:
> > > The meta-virt recipe had the same _1.0.bb extension, and it's SRCREV
> lines up
> > > with the openflow-1.0.0 tag in the repository:
> > >
> > > --------
> > >
> > > commit 5ccca75a69f99791659bcfbcf35353ab1921320a
> > > Author: Glen Gibb <grg at stanford.edu>
> > > Date:   Thu Dec 31 16:00:53 2009 -0800
> > >
> > >     docs: Update ChangeLog to include 1.0.0 information
> > >
> > > :100644 100644 2f13dd7... aa0e92e... M  ChangeLog
> > >
> > > -------
> > >
> > > So it's definitely an option to keep that recipe around as the tagged
> 1.0, and
> > > create a _git that tracks newer changes (where "newer" is relative,
> 2011 is
> > > the latest commit in that repo).
> >
> > FWIW, I massively prefer "releases that are taken from git" like this
> > (where its a git fetch on a hash that is the tag of the releases) to
> > be versioned correctly like _1.0.bb instead of _git.bb for clarity and
> > future alternatives such as true git snapshot or multiple versions.
>
> Yeah, since the SRCREV in the _1.0.bb recipe actually corresponds to the
> 1.0 release tag, I'm in agreement.  The proposed update from Laszlo also
> now seems to justify having a _git.bb version, since it's pointing at a
> (relatively) newer version of the recipe.
>
> --
> -Joe MacDonald.
> :wq
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>