From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga09.intel.com ([134.134.136.24]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1RgKgH-0000eH-5F for openembedded-devel@lists.openembedded.org; Thu, 29 Dec 2011 19:26:22 +0100 Received: from mail-tul01m020-f180.google.com ([209.85.214.180]) by mga09.intel.com with ESMTP/TLS/RC4-SHA; 29 Dec 2011 10:19:05 -0800 Received: by obbup3 with SMTP id up3so9072547obb.25 for ; Thu, 29 Dec 2011 10:19:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.222.233 with SMTP id qp9mr42485804igc.1.1325182744241; Thu, 29 Dec 2011 10:19:04 -0800 (PST) Received: by 10.50.208.98 with HTTP; Thu, 29 Dec 2011 10:19:04 -0800 (PST) In-Reply-To: References: <1324003173-13994-1-git-send-email-b19537@freescale.com> <1324003173-13994-5-git-send-email-b19537@freescale.com> <44FD6890-C4DA-4A40-B30F-BDADC690C21E@dominion.thruhere.net> <20111216215455.GC28832@sakrah.homelinux.org> Date: Thu, 29 Dec 2011 10:19:04 -0800 Message-ID: From: "Flanagan, Elizabeth" To: Luo Zhenhua-B19537 Cc: "openembedded-devel@lists.openembedded.org" Subject: Re: [PATCH meta-oe 5/9] nerperf: add X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 18:26:23 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Dec 21, 2011 at 6:44 PM, Luo Zhenhua-B19537 wrote: > May I know which license type should be put in the recipe? > > LICENSE =3D "GPLv2+" > > Or > > LICENSE =3D "Netperf 4" No, what I meant was, look at the version of Netperf, called Netperf 4. http://www.netperf.org/svn/netperf4/ It's license would be GPL-2.0+. > > > > > > Best Regards, > > > > Zhenhua > > > > From: Flanagan, Elizabeth [mailto:elizabeth.flanagan@intel.com] > Sent: Thursday, December 22, 2011 1:38 AM > To: Luo Zhenhua-B19537 > Cc: openembedded-devel@lists.openembedded.org > > Subject: Re: [oe] [PATCH meta-oe 5/9] nerperf: add > > > > > > On Tue, Dec 20, 2011 at 10:26 PM, Luo Zhenhua-B19537 > wrote: > > I have sent an email to netperf-feedback@netperf.org to query the > appropriate license type yesterday and not response. > > I'd like to adopt following option, does it make sense? > >> > 2. We'll need to add a Netperf license to common-licenses and set >> > LICENSE =3D "Netperf" > > > Yes, I agree. Although the Netperf license isn't really compatible with a= ny > OSI compliant license I know of and may cause end user problems. One opti= on > is to use Netperf 4 which is in fact GPL compliant. In that case it would= be > licensed as LICENSE =3D "GPL-2.0+" > > If netperf 4 was equivalent from a functional standpoint, I'd go consider > route, as the Netperf 2.x.x license can be problematic for some end users= , > I'm sure. > > -b > > > > Best Regards, > > Zhenhua > > >> -----Original Message----- > >> From: Luo Zhenhua-B19537 >> Sent: Tuesday, December 20, 2011 10:32 AM >> To: openembedded-devel@lists.openembedded.org >> Subject: RE: [oe] [PATCH meta-oe 5/9] nerperf: add >> >> Thanks for the feedback. >> >> I saw netperf is licensed under "netperf" in oe >> >> http://cgit.openembedded.org/openembedded/plain/recipes/netperf/netperf_= 2.4.4.bb. >> >> Anyway, I will send an email to the author to query about the license >> type. >> >> >> Best Regards, >> >> Zhenhua >> >> > -----Original Message----- >> > From: Flanagan, Elizabeth [mailto:elizabeth.flanagan@intel.com] >> > Sent: Tuesday, December 20, 2011 6:32 AM >> > To: openembedded-devel@lists.openembedded.org; Luo Zhenhua-B19537 >> > Subject: Re: [oe] [PATCH meta-oe 5/9] nerperf: add >> > > >> > On Fri, Dec 16, 2011 at 1:54 PM, Khem Raj wrote: >> > > On (16/12/11 10:22), Koen Kooi wrote: >> > >> >> > >> Op 16 dec. 2011, om 10:19 heeft Luo Zhenhua-B19537 het volgende >> > >> geschreven: >> > >> >> > >> > Hello Koen, >> > >> > >> > >> >> -----Original Message----- >> > >> >> From: openembedded-devel-bounces@lists.openembedded.org >> > >> >> [mailto:openembedded- devel-bounces@lists.openembedded.org] On >> > >> >> Behalf Of Koen Kooi >> > >> >> Sent: Friday, December 16, 2011 3:52 PM >> > >> >> >> > >> >>> +++ b/meta-oe/recipes-benchmark/netperf/netperf_2.4.4.bb @@ > >> > >> >>> +++ -0,0 >> > >> >>> +++ +1,47 > >> > >> >>> @@ +DESCRIPTION=3D"Network performance benchmark including test= s >> > >> >>> for TCP, UDP, sockets, ATM and more." +SECTION =3D >> > >> >>> "console/network" >> > >> >>> +HOMEPAGE =3D "http://www.netperf.org/" +LICENSE =3D "netperf" >> > >> >> >> > >> >> Can you include a comment on what type of license netperf is? >> > >> >> MIT like, BSD like, GPL like? >> > >> > [Luo Zhenhua-B19537] May I know which license type should be with >> > >> > following >> > COPYING content? >> > >> >> > >> That looks like a BSD or MIT derivative, maybe Beth can give us >> > >> some guidance on what to use as LICENSE >> > > >> > > it says "for non-commercial purposes only" >> > >> > Yeah.... in this case, I would do one of two things (and I have a >> > feeling one will be more valid that the other): >> > >> > 1. Email the author and see if we can use BSD-4-Clause. My guess is no= . >> > 2. We'll need to add a Netperf license to common-licenses and set >> > LICENSE =3D "Netperf" >> > >> > I've checked the openSuSE Build Service and they have this as an >> > "Other" license, so, check with the author first, but be prepared to > >> > add Netperf to the common- licenses directory. > >> > >> > And yes, Koen is right. I wouldn't use BSD or MIT for this, >> > specifically because of the non-commercial clause in (ii). >> > >> > -b >> > >> > > >> > >> >> > >> regards, >> > >> >> > >> Koen >> > >> >> > >> >> > >> > >> > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0Copyright (C) 1993 Hewlett-Packard Com= pany >> > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ALL RIGHTS RESERV= ED. >> > >> > >> > >> > =A0The enclosed software and documentation includes copyrighted >> > >> > works >> > >> > =A0of Hewlett-Packard Co. For as long as you comply with the >> > >> > following >> > >> > =A0limitations, you are hereby authorized to (i) use, reproduce, >> > >> > and >> > >> > =A0modify the software and documentation, and to (ii) distribute >> > >> > the >> > >> > =A0software and documentation, including modifications, for >> > >> > =A0non-commercial purposes only. >> > >> > >> > >> > =A01. =A0The enclosed software and documentation is made availabl= e at >> > >> > no >> > >> > =A0 =A0 =A0charge in order to advance the general development of >> > >> > =A0 =A0 =A0high-performance networking products. >> > >> > >> > >> > =A02. =A0You may not delete any copyright notices contained in th= e >> > >> > =A0 =A0 =A0software or documentation. All hard copies, and copies= in >> > >> > =A0 =A0 =A0source code or object code form, of the software or >> > >> > =A0 =A0 =A0documentation (including modifications) must contain a= t >> > >> > least >> > >> > =A0 =A0 =A0one of the copyright notices. >> > >> > >> > >> > =A03. =A0The enclosed software and documentation has not been >> > >> > subjected >> > >> > =A0 =A0 =A0to testing and quality control and is not a Hewlett-Pa= ckard >> > >> > Co. >> > >> > =A0 =A0 =A0product. At a future time, Hewlett-Packard Co. may or = may >> > >> > not >> > >> > =A0 =A0 =A0offer a version of the software and documentation as a >> > >> > product. >> > >> > >> > >> > =A04. =A0THE SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS". >> > >> > =A0 =A0 =A0HEWLETT-PACKARD COMPANY DOES NOT WARRANT THAT THE USE, >> > >> > =A0 =A0 =A0REPRODUCTION, MODIFICATION OR DISTRIBUTION OF THE SOFT= WARE >> > >> > OR >> > >> > =A0 =A0 =A0DOCUMENTATION WILL NOT INFRINGE A THIRD PARTY'S INTELL= ECTUAL >> > >> > =A0 =A0 =A0PROPERTY RIGHTS. HP DOES NOT WARRANT THAT THE SOFTWARE= OR >> > >> > =A0 =A0 =A0DOCUMENTATION IS ERROR FREE. HP DISCLAIMS ALL WARRANTI= ES, >> > >> > =A0 =A0 =A0EXPRESS AND IMPLIED, WITH REGARD TO THE SOFTWARE AND T= HE >> > >> > =A0 =A0 =A0DOCUMENTATION. HP SPECIFICALLY DISCLAIMS ALL WARRANTIE= S OF >> > >> > =A0 =A0 =A0MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. >> > >> > >> > >> > =A05. =A0HEWLETT-PACKARD COMPANY WILL NOT IN ANY EVENT BE LIABLE = FOR >> > >> > ANY >> > >> > =A0 =A0 =A0DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL >> > >> > DAMAGES >> > >> > =A0 =A0 =A0(INCLUDING LOST PROFITS) RELATED TO ANY USE, REPRODUCT= ION, >> > >> > =A0 =A0 =A0MODIFICATION, OR DISTRIBUTION OF THE SOFTWARE OR >> > >> > DOCUMENTATION. >> > >> > >> > >> > >> > >> > Best Regards, >> > >> > >> > >> > Zhenhua >> > >> > >> > >> >> > > >> > > >> > > >> > >> _______________________________________________ >> > >> Openembedded-devel mailing list >> > >> Openembedded-devel@lists.openembedded.org >> > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-de >> > >> ve >> > >> l >> > > >> > > >> > > -- >> > > -Khem >> > > >> > > _______________________________________________ >> > > Openembedded-devel mailing list >> > > Openembedded-devel@lists.openembedded.org >> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev >> > > el >> > >> > >> > >> > -- >> > Elizabeth Flanagan >> > Yocto Project >> > Build and Release > > > > > -- > Elizabeth Flanagan > Yocto Project > Build and Release --=20 Elizabeth Flanagan Yocto Project Build and Release