Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Liu Ting-B28495 <B28495@freescale.com>,
	Guo Chunrong-B40290 <B40290@freescale.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] common-licenses: Adding netperf
Date: Tue, 09 Jul 2013 12:14:28 +0100	[thread overview]
Message-ID: <1899518.lrLlCUV9nm@helios> (raw)
In-Reply-To: <AF604684617F454390621992F367F1690BA97FAF@039-SN2MPN1-011.039d.mgd.msft.net>

On Tuesday 09 July 2013 08:01:58 Liu Ting-B28495 wrote:
> Netperf is restricted license. I don't think oe-core will accept it.
> 
> We add below line in fsl-setup-poky:
> echo "# whiteliste restricted license" >> conf/local.conf
> echo "LICENSE_FLAGS_WHITELIST = \"non-commercial_netperf\"" >>
> conf/local.conf
> 
> -Ting
> 
> > -----Original Message-----
> > From: Guo Chunrong-B40290
> > Sent: Tuesday, July 09, 2013 3:47 PM
> > To: openembedded-core@lists.openembedded.org
> > Cc: Liu Ting-B28495; Luo Zhenhua-B19537; Guo Chunrong-B40290; Guo
> > Chunrong-B40290
> > Subject: [OE-core][PATCH] common-licenses: Adding netperf
> > 
> >        *netperf requires it's own specific license when
> >        add meta-openembedded layer
> > 
> > Signed-off-by: Chunrong Guo <B40290@freescale.com>
> > ---
> > 
> >  meta/files/common-licenses/netperf |   43
> > 
> > ++++++++++++++++++++++++++++++++++++
> > 
> >  1 files changed, 43 insertions(+), 0 deletions(-)  create mode 100644
> > 
> > meta/files/common-licenses/netperf
> > 
> > diff --git a/meta/files/common-licenses/netperf b/meta/files/common-
> > licenses/netperf
> > new file mode 100644
> > index 0000000..3f3ceb2
> > --- /dev/null
> > +++ b/meta/files/common-licenses/netperf
> > @@ -0,0 +1,43 @@
> > +
> > +
> > +              Copyright (C) 1993 Hewlett-Packard Company
> > +                         ALL RIGHTS RESERVED.
> > +
> > +  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.
> > +
> > +  1.  The enclosed software and documentation is made available at no
> > +      charge in order to advance the general development of
> > +      high-performance networking products.
> > +
> > +  2.  You may not delete any copyright notices contained in the
> > +      software or documentation. All hard copies, and copies in
> > +      source code or object code form, of the software or
> > +      documentation (including modifications) must contain at least
> > +      one of the copyright notices.
> > +
> > +  3.  The enclosed software and documentation has not been subjected
> > +      to testing and quality control and is not a Hewlett-Packard Co.
> > +      product. At a future time, Hewlett-Packard Co. may or may not
> > +      offer a version of the software and documentation as a product.
> > +
> > +  4.  THE SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS".
> > +      HEWLETT-PACKARD COMPANY DOES NOT WARRANT THAT THE USE,
> > +      REPRODUCTION, MODIFICATION OR DISTRIBUTION OF THE SOFTWARE OR
> > +      DOCUMENTATION WILL NOT INFRINGE A THIRD PARTY'S INTELLECTUAL
> > +      PROPERTY RIGHTS. HP DOES NOT WARRANT THAT THE SOFTWARE OR
> > +      DOCUMENTATION IS ERROR FREE. HP DISCLAIMS ALL WARRANTIES,
> > +      EXPRESS AND IMPLIED, WITH REGARD TO THE SOFTWARE AND THE
> > +      DOCUMENTATION. HP SPECIFICALLY DISCLAIMS ALL WARRANTIES OF
> > +      MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
> > +
> > +  5.  HEWLETT-PACKARD COMPANY WILL NOT IN ANY EVENT BE LIABLE FOR ANY
> > +      DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
> > +      (INCLUDING LOST PROFITS) RELATED TO ANY USE, REPRODUCTION,
> > +      MODIFICATION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION.
> > +
> > +
> > --

The answer here may be that the layer that adds the recipe (meta-networking in 
this case) should add the license rather than it being added to OE-Core. To do 
this, add the following to the layer's conf/layer.conf:

LICENSE_PATH += "${LAYERDIR}/licenses"

Then put the netperf file in a "licenses" subdirectory within the layer.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-07-09 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  7:46 [PATCH] common-licenses: Adding netperf Chunrong Guo
2013-07-09  8:01 ` Liu Ting-B28495
2013-07-09 11:14   ` Paul Eggleton [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=1899518.lrLlCUV9nm@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=B28495@freescale.com \
    --cc=B40290@freescale.com \
    --cc=openembedded-core@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