From: Darren Hart <dvhart@linux.intel.com>
To: tom.zanussi@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 10/12] meta-fri2: make the use of emgd-driver-bin COMMERCIAL
Date: Wed, 17 Aug 2011 10:25:30 -0700 [thread overview]
Message-ID: <4E4BF98A.5090501@linux.intel.com> (raw)
In-Reply-To: <0bb19ed262106171280812cbd463b6697e848d4d.1313598804.git.tom.zanussi@intel.com>
On 08/17/2011 09:51 AM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> The emgd-driver-bin recipe now automatically downloads and installs
> EMGD using the new click-through-free tarball, but since the binaries
> still fall under a non-free license, we need to prevent it from being
> accidentally installed in an image.
>
> We therefore make sure it's labeled in the fri2 layer with
> 'COMMERCIAL_LICENSE'. In order to build an fri2 image, the user
> now needs to add a 'COMMERCIAL_LICENSE = ""' line to local.conf.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> meta-fri2/conf/layer.conf | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta-fri2/conf/layer.conf b/meta-fri2/conf/layer.conf
> index 261cccc..eb17336 100644
> --- a/meta-fri2/conf/layer.conf
> +++ b/meta-fri2/conf/layer.conf
> @@ -10,3 +10,5 @@ BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
> BBFILE_COLLECTIONS += "fri2"
> BBFILE_PATTERN_fri2 := "^${LAYERDIR}/"
> BBFILE_PRIORITY_fri2 = "6"
> +
> +COMMERCIAL_LICENSE += "emgd-driver-bin"
Can't this be done in the common emgd driver recipe? Seems wrong to have
to specify commercial license for recipe in a machine config... A
different machine could just omit it and the user would not have to add
COMMERCIAL_LICENSE = "" to their local.conf and it would be fine?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-08-17 17:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 16:51 [PATCH 00/12] meta-intel: EMGD 1.8 and 3.0 kernel upgrade, v2 tom.zanussi
2011-08-17 16:51 ` [PATCH 01/12] meta-crownbay: switch to linux-yocto 3.0 kernel tom.zanussi
2011-08-17 16:51 ` [PATCH 02/12] meta-crownbay: new recipe for emgd 1.8 driver binaries tom.zanussi
2011-08-17 16:51 ` [PATCH 03/12] meta-crownbay: select emgd 1.8 tom.zanussi
2011-08-17 16:51 ` [PATCH 04/12] meta-crownbay: make the use of emgd-driver-bin COMMERCIAL tom.zanussi
2011-08-17 16:51 ` [PATCH 05/12] meta-crownbay: xorg.conf changes tom.zanussi
2011-08-17 16:51 ` [PATCH 06/12] meta-crownbay: update README tom.zanussi
2011-08-18 18:12 ` Saul Wold
2011-08-18 18:53 ` Tom Zanussi
2011-08-19 13:53 ` Tom Zanussi
2011-08-17 16:51 ` [PATCH 07/12] meta-fri2: add EMGD 1.8 capabilities to fri2 tom.zanussi
2011-08-17 16:51 ` [PATCH 08/12] meta-intel: move emgd-driver-bin_1.8 to common tom.zanussi
2011-08-17 16:51 ` [PATCH 09/12] meta-fri2: add common/recipes-graphics to BBFILES tom.zanussi
2011-08-17 16:51 ` [PATCH 10/12] meta-fri2: make the use of emgd-driver-bin COMMERCIAL tom.zanussi
2011-08-17 17:25 ` Darren Hart [this message]
2011-08-17 19:26 ` Tom Zanussi
2011-08-17 19:31 ` Darren Hart
2011-08-17 16:51 ` [PATCH 11/12] meta-fri2: update README tom.zanussi
2011-08-17 16:51 ` [PATCH 12/12] meta-intel: crownbay/fri2 README update for COMMERCIAL_LICENSE tom.zanussi
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=4E4BF98A.5090501@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@yoctoproject.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 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.