From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: netperf in meta-networking
Date: Fri, 30 Nov 2012 12:56:22 -0500 [thread overview]
Message-ID: <20121130175622.GT6912@windriver.com> (raw)
In-Reply-To: <5531449.L0Ch4936zy@helios>
[-- Attachment #1: Type: text/plain, Size: 3181 bytes --]
[Re: [oe] netperf in meta-networking] On 12.11.30 (Fri 16:55) Paul Eggleton wrote:
> On Friday 30 November 2012 11:34:11 Joe MacDonald wrote:
> > [netperf in meta-networking] On 12.11.30 (Fri 10:18) Mark Hatle wrote:
> > > I was helping someone with building netperf from meta-networking
> > > last night, and stumbled on what I think is a bug.
> > >
> > > SUMMARY = "A networking benchmarking tool"
> > > DESCRIPTION = "Network performance benchmark including tests for
> > > TCP, UDP, sockets, ATM and more."
> > > SECTION = "console/network"
> > > HOMEPAGE = "http://www.netperf.org/"
> > > LICENSE = "netperf"
> > > LICENSE_FLAGS = "commercial"
> > >
> > > In the above, the LICENSE_FLAGS are set to 'commercial'. I think
> > > this is incorrect. It should be set to 'non-commercial'.
> > >
> > > There is a subtle difference between them which is why I think it's a
> > > bug...
> > >
> > > commercial -- there are some commercial requirements necessary to
> > > use this recipe in a commercial device... you are responsible for
> > > understanding them and doing whatever is necessary... (for
> > > non-commercial devices you can likely use it...)
> > >
> > > non-commercial -- this item is restricted to non-commercial users
> > > only. As in the case of netperf, the license says it's only for
> > > non-commercial use.
> > >
> > > So anyway, my suggestion is to simply change the value of the flag.
> >
> > Ugh. I had a quick look around and the first thing I found was this:
> >
> > http://www.netperf.org/svn/netperf4/trunk/include/netperf.h
>
> This is netperf4 though which I gather is distinct from the version of
> netperf we are building.
Yeah, that's what had me going back to the documentation in the tarball,
since given the previous license, this one is worlds apart even though
it's coming from the same folks.
> > So I had a look at the netperf source tree fetched by bitbake during a
> > build. The COPYING file says this:
> >
> > The enclosed software and documentation includes copyrighted works
> > of Hewlett-Packard Co. For as long as you comply with the following
> > limitations, you are hereby authorized to (i) use, reproduce, and
> > modify the software and documentation, and to (ii) distribute the
> > software and documentation, including modifications, for
> > non-commercial purposes only.
> >
> > So I'm inclined to agree, this sounds like the definition of
> > non-commercial above to me.
>
> It's a subtlety - in either case you can't just go ahead and use it for
> commercial use. I wouldn't object to changing it to "non-commercial" though if
> it makes more sense.
>
> Would it be practical for us to move to netperf4 which is GPLv2+ licensed? I'm
> not sure if it is a complete replacement for netperf 2.x and we'd need to
> confirm that first, but at least the license is more reasonable...
I would be happy to see a netperf4-based recipe show up, but I don't
currently have any plans for one. It would certainly be nice to have
both available, though, since 4 is not a complete replacement for 2.x.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-11-30 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 16:18 netperf in meta-networking Mark Hatle
2012-11-30 16:34 ` Joe MacDonald
2012-11-30 16:54 ` Joe MacDonald
2012-11-30 16:55 ` Paul Eggleton
2012-11-30 17:11 ` Mark Hatle
2012-11-30 17:56 ` Joe MacDonald [this message]
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=20121130175622.GT6912@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.