[meta-freescale] [fsl-community-bsp-base][PATCH v3] setup-environment: Update pre-EULA language to support older licenses.

Lauren Post Lauren.Post at freescale.com
Tue Jun 9 20:32:08 PDT 2015


I checked with our lawyer again today and she thinks the wording is clear and is not willing to make further changes.

I have presented your request to her but I'll have to stick with the current wording.

If there is any confusion, the EULA is more detailed.


-----Original Message-----
From: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] On Behalf Of Otavio Salvador
Sent: Monday, June 08, 2015 11:33 AM
To: Post Lauren-RAA013
Cc: meta-freescale at yoctoproject.org
Subject: Re: [meta-freescale] [fsl-community-bsp-base][PATCH v3] setup-environment: Update pre-EULA language to support older licenses.

On Mon, Jun 8, 2015 at 11:51 AM, Lauren Post <lauren.post at freescale.com> wrote:
> Some legacy packages will contain older versions of licenses.   This language
> explains that the conflict in license should use the license in package.
> v3: Changed language to avoid confusion with open source

This should be below --- so it is not part of the commit log.

> Signed-off-by: Lauren Post <lauren.post at freescale.com>
> ---
>  setup-environment |   14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> diff --git a/setup-environment b/setup-environment index 
> 7034cc5..24ee678 100755
> --- a/setup-environment
> +++ b/setup-environment
> @@ -186,9 +186,17 @@ fi
>  if [ "$EULA" = "ask" ]; then
>      cat <<EOF
> -Some BSPs depend on libraries and packages which are covered by 
> Freescale's -End User License Agreement (EULA). To have the right to 
> use these binaries in -your images, you need to read and accept the following...
> +Proprietary and third party software is subject to agreement and 
> +compliance with, Freescale's End User License Agreement. To have the 
> +right to use these binaries in your images, you must read and accept the following terms.

This part looks fine for me.

>  If
> +there are conflicting terms embedded in the software, the terms 
> +embedded in the Software will control.

I would drop this.

> +In all cases,  open source software is licensed under the terms of 
> +the applicable open source license(s), such as the BSD License, 
> +Apache License or the GNU Lesser General Public License.  Your use of 
> +the open source software is subject to the terms of each applicable 
> +license.  You must agree to the terms of each applicable license, or you cannot use the open source software.

I think a guard is missing here. Something like:

... and by no means the use of the open source software can negate or override a rule included in the Freescale's End User License Agreement (EULA).

The lawyer certainly can provide a more elaborated text but making it clear seems to be good.

Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

More information about the meta-freescale mailing list