From eb26831edd3c32977a045d22acae3a36cca696eb Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 29 Mar 2013 08:43:34 -0700 Subject: ref-manual: Edits to the License Compliance question. (From yocto-docs rev: bdf123ae728ff5725831dab5d5e0505bbb56bac2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/faq.xml | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) (limited to 'documentation/ref-manual/faq.xml') diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index 8884dba663..e4cca269ca 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml @@ -377,13 +377,22 @@ - This is a difficult question and you need to consult your lawyer for the answer - for your specific case. - It is worth bearing in mind that for GPL compliance there needs to be enough - information shipped to allow someone else to rebuild the same end result - you are shipping. - This means sharing the source code, any patches applied to it, and also any - configuration information about how that package was configured and built. + This is a difficult question and you need to consult your lawyer + for the answer for your specific case. + It is worth bearing in mind that for GPL compliance, there needs + to be enough information shipped to allow someone else to + rebuild and produce the same end result you are shipping. + This means sharing the source code, any patches applied to it, + and also any configuration information about how that package + was configured and built. + + + + You can find more information on licensing in the + "Licensing" + and "Maintaining Open Source License Compliance During Your Product's Lifecycle" + sections, both of which are in the Yocto Project Development + Manual. -- cgit v1.2.3-54-g00ecf