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
Signed-off-by: Lauren Post <lauren.p...@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. If
+there are conflicting terms embedded in the software, the terms embedded in
+the Software will control.
+
+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.
EOF
--
1.7.9.5
--
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
