From 3c02a88337baafadcee571e1990939ccec5eb356 Mon Sep 17 00:00:00 2001 From: Rahul Bedarkar Date: Mon, 25 Jan 2016 10:35:40 +0530 Subject: [PATCH] docs/manual: document format for specifying licenses Signed-off-by: Rahul Bedarkar [Thomas: minor tweaks for clarity.] Signed-off-by: Thomas Petazzoni --- docs/manual/adding-packages-generic.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt index b7817e309c..8ed7fe8ee2 100644 --- a/docs/manual/adding-packages-generic.txt +++ b/docs/manual/adding-packages-generic.txt @@ -387,7 +387,16 @@ information is (assuming the package name is +libfoo+) : Otherwise, describe the license in a precise and concise way, avoiding ambiguous names such as +BSD+ which actually name a family of licenses. This variable is optional. If it is not defined, +unknown+ will appear in - the +license+ field of the manifest file for this package. + the +license+ field of the manifest file for this package. + + The expected format for this variable must comply with the following rules: + ** If different parts of the package are released under different + licenses, then +comma+ separate licenses (e.g. +`LIBFOO_LICENSE = + GPLv2+, LGPLv2.1+`+). If there is clear distinction between which + component is licensed under what license, then annotate the license + with that component, between parenthesis (e.g. +`LIBFOO_LICENSE = + GPLv2+ (programs), LGPLv2.1+ (libraries)`+). + ** If the package is dual licensed, then separate licenses with the + +or+ keyword (e.g. +`LIBFOO_LICENSE = AFLv2.1 or GPLv2+`+). * +LIBFOO_LICENSE_FILES+ is a space-separated list of files in the package tarball that contain the license(s) under which the package is released.