From 8c42eaa2e09d5e9fe42cd0a4231fecf38fa513fd Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Mon, 25 Apr 2022 19:06:47 +0200 Subject: overview-manual: licensing section fixes Remove the reference to the GPL license, unnecessary in this part of the manual and pointing to a wrong link (LGPL instead of GPL). Anyway, we have no authority to say that the MIT license is compatible with the GPL. Also provide details about the MIT license through Wikipedia, instead of just the raw license text with no explanations through opensource.org. (From yocto-docs rev: a09fcd9d850d2b52f40d953b11412c9568a77db7) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/overview-manual/development-environment.rst | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'documentation/overview-manual') diff --git a/documentation/overview-manual/development-environment.rst b/documentation/overview-manual/development-environment.rst index 19095fc116..e171d7aaa3 100644 --- a/documentation/overview-manual/development-environment.rst +++ b/documentation/overview-manual/development-environment.rst @@ -616,13 +616,9 @@ this history, you can find basic information here: In general, the Yocto Project is broadly licensed under the Massachusetts Institute of Technology (MIT) License. MIT licensing permits the reuse of software within proprietary software as long as the -license is distributed with that software. MIT is also compatible with -the GNU General Public License (GPL). Patches to the Yocto Project +license is distributed with that software. Patches to the Yocto Project follow the upstream licensing scheme. You can find information on the -MIT license -`here `__. You can -find information on the GNU GPL -`here `__. +MIT license `here `__. When you build an image using the Yocto Project, the build process uses a known list of licenses to ensure compliance. You can find this list in -- cgit v1.2.3-54-g00ecf