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

[Laszlo Papp]

On Thu, Sep 5, 2013 at 10:01 AM, Burton, Ross <ross.burton at intel.com> 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.
>

... and I massively prefer "released not to be taken from git". So if 1.0
has to be *really* supported which I do not think so, it should get the
release tarball.

Moreover, there have not been new git commits for about two years now
because the standard was taken over by a different organization which seems
to work behind the scenes. Too bad, they have not released the latest
before that change. Hopefully, this will not mislead anyone that this
software is still actively developed in public.

That is another very reason IMHO which it would not fit the core layer at
all.

-- Laszlo


>
> Ross
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>