From 78564304dc23b4312ee4f7a836a26ecdde88e11e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 9 Jan 2014 07:58:24 -0600 Subject: dev-manual: Edits to the "Licensing" section. Applied review comments to this section per Paul Eggleton. Minor word changes. (From yocto-docs rev: 5130559003778e3b613d3d480350d041dfd10fcd) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index c5ff3b29b5..3ee327c54d 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1633,7 +1633,7 @@ LICENSE: This variable specifies the license for the software. If you do not know the license under which the software - you are building is distributed, you can go to the + you are building is distributed, you should go to the source code and look for that information. Typical files containing this information include COPYING, @@ -1641,17 +1641,16 @@ README files. You could also find the information near the top of a source file. - The key is to find something that states the public - license needed for the software. For example, given a piece of software licensed under the GNU General Public License version 2, you would set LICENSE as follows: LICENSE = "GPLv2" - The licenses you specify with - LICENSE be any name as long as - you do not use spaces. + The licenses you specify within + LICENSE can have any name as long + as you do not use spaces, since spaces are used as + separators between license names. For standard licenses, use the names of the files in meta/files/common-licenses/ or the SPDXLICENSEMAP flag names -- cgit v1.2.3-54-g00ecf