On Wed, Sep 4, 2013 at 5:14 PM, Joe MacDonald <[email protected]> wrote: > Actually, after all of that, I do have a couple of additional requests > (beyond just the tweak to the commit log). > > Explicitly cc:ing Bruce here since I'm intentionally not adding > meta-virt@. I've gotten bounced from it in the past as I'm not a > subscriber and it's subscriber-only.
:) I can't blame you for that, I share the pain (after bouncing off of oe-devel just a few days ago myself). Thanks for the cc. > > [[oe] [meta-networking][PATCH] openflow: Add latest from git] On 13.09.02 > (Mon 09:20) Laszlo Papp wrote: > >> 1) The version in meta-virtualization is quite old. It is basically from >> 2009, >> and a lot of things has changed since then. >> >> 2) More importantly, this software is more like for networking rather than >> virtualization, so I think it was misplaced. > > SOB please? > >> --- >> .../recipes-support/openflow/openflow_1.0.bb | 32 >> ++++++++++++++++++++++ > > Is this actually based on an OpenFlow 1.0 release, or has it always been > 1.0+git? I don't have a copy of meta-virt around to check myself. If > there was a real 1.0 recipe around, can we keep it as is and make this > openflow_git.bb, more in line with the other +git... recipes? 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 <[email protected]> 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). Maybe someday, we'll get a working 1.x openflow to play with! :) Thanks for holding on this briefly, it did help. Bruce > >> 1 file changed, 32 insertions(+) >> create mode 100644 meta-networking/recipes-support/openflow/openflow_1.0.bb >> >> diff --git a/meta-networking/recipes-support/openflow/openflow_1.0.bb >> b/meta-networking/recipes-support/openflow/openflow_1.0.bb >> new file mode 100644 >> index 0000000..eb7770e >> --- /dev/null >> +++ b/meta-networking/recipes-support/openflow/openflow_1.0.bb >> @@ -0,0 +1,32 @@ >> +SUMMARY = "OpenFlow" >> +DESCRIPTION = "Open standard that enables researchers to run experimental >> protocols in the campus networks" >> +HOMEPAGE = "http://www.openflow.org"; >> +SECTION = "networking" >> +LICENSE = "GPLv2" >> + >> +LIC_FILES_CHKSUM = "file://COPYING;md5=e870c934e2c3d6ccf085fd7cf0a1e2e2" >> + >> +SRCREV = "c84f33f09d5dbcfc9b489f64cb30475bf36f653a" >> +PV = "1.0+git${SRCPV}" >> +SRC_URI = "git://gitosis.stanford.edu/openflow.git;protocol=git" >> + >> +DEPENDS = "virtual/libc" >> + >> +EXTRA_OECONF += "KARCH=${TARGET_ARCH}" >> + >> +PACKAGECONFIG ??= "libssl" >> +PACKAGECONFIG[libssl] = "--enable-ssl,--disable-ssl, openssl, libssl" >> + >> +S = "${WORKDIR}/git" >> + >> +inherit autotools >> + >> +do_configure() { >> + ./boot.sh >> + oe_runconf >> +} >> + >> +do_install_append() { >> + # Remove /var/run as it is created on startup >> + rm -rf ${D}${localstatedir}/run >> +} > > And while we're in the neighbourhood, can we also clean up the > inconsistent spacing? > > Thanks. > > -- > -Joe MacDonald. > :wq > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
