Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iperf: add license information
Date: Tue, 20 Jan 2015 13:09:18 +0200	[thread overview]
Message-ID: <20150120110918.GE2146@tarshish> (raw)
In-Reply-To: <CACQ1gAimqif=SX4yJqFOqyrto-aPEzF5EyY7S9JHgY5-QDU8MA@mail.gmail.com>

Hi Richard,

On Tue, Jan 20, 2015 at 12:03:06PM +0100, Richard Genoud wrote:
> 2015-01-20 11:51 GMT+01:00 Baruch Siach <baruch@tkos.co.il>:
> > On Tue, Jan 20, 2015 at 11:15:06AM +0100, Richard Genoud wrote:
> >> Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
> >> ---
> >>  package/iperf/iperf.mk | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/package/iperf/iperf.mk b/package/iperf/iperf.mk
> >> index 2947e5241974..4ec56e0f2c23 100644
> >> --- a/package/iperf/iperf.mk
> >> +++ b/package/iperf/iperf.mk
> >> @@ -6,6 +6,7 @@
> >>
> >>  IPERF_VERSION = 2.0.5
> >>  IPERF_SITE = http://downloads.sourceforge.net/project/iperf
> >> +IPERF_LICENSE_FILES = COPYING
> >
> > Missing IPERF_LICENSE.
> 
> damned !
> you're right, I forgot that.
> 
> hum... and now that I read the COPYING file, I understand why I didn't
> fill the IPERF_LICENSE : it's not a "known" license :
> Copyright (c) 1999-2007, The Board of Trustees of the University of Illinois
> All Rights Reserved.
> 
> Iperf performance test
> Mark Gates
> Ajay Tirumala
> Jim Ferguson
> Jon Dugan
> Feng Qin
> Kevin Gibbs
> John Estabrook
> National Laboratory for Applied Network Research
> National Center for Supercomputing Applications
> University of Illinois at Urbana-Champaign
> http://www.ncsa.uiuc.edu
> 
> Permission is hereby granted, free of charge, to any person obtaining a copy
> of this software (Iperf) and associated documentation files (the "Software"),
> to deal in the Software without restriction, including without limitation the
> rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
> sell copies of the Software, and to permit persons to whom the Software is
> furnished to do so, subject to the following conditions:
> 
> 
> Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimers.
> 
> Redistributions in binary form must reproduce the above copyright notice, this
> list of conditions and the following disclaimers in the documentation and/or
> other materials provided with the distribution.
> 
> Neither the names of the University of Illinois, NCSA, nor the names of its
> contributors may be used to endorse or promote products derived from this
> Software without specific prior written permission.  THE SOFTWARE IS PROVIDED
> "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
> LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
> AND NONINFRINGEMENT. IN NO EVENT SHALL THE CONTIBUTORS OR COPYRIGHT HOLDERS BE
> LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
> CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
> SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
> 
> 
> So, should I call it "Iperf 2.x license" ?

Looks very similar to the MIT license (http://opensource.org/licenses/MIT). 
IANAL, though.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-01-20 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 10:15 [Buildroot] [PATCH] iperf: add license information Richard Genoud
2015-01-20 10:51 ` Baruch Siach
2015-01-20 11:03   ` Richard Genoud
2015-01-20 11:09     ` Baruch Siach [this message]
2015-01-20 11:14       ` Richard Genoud

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=20150120110918.GE2146@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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