From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Joe MacDonald <joe.macdonald@windriver.com>
Subject: netperf in meta-networking
Date: Fri, 30 Nov 2012 10:18:34 -0600 [thread overview]
Message-ID: <50B8DC5A.7050203@windriver.com> (raw)
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.
--Mark
next reply other threads:[~2012-11-30 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 16:18 Mark Hatle [this message]
2012-11-30 16:34 ` netperf in meta-networking 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
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=50B8DC5A.7050203@windriver.com \
--to=mark.hatle@windriver.com \
--cc=joe.macdonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox