From 4c00602eb5bb67f30b2d344ac9bd0d57532c0174 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 16 Apr 2013 13:06:58 -0700 Subject: dev-manual: Edits to "Maintaining Open Source License Compliance During Your Product's Lifecycle" section. (From yocto-docs rev: 3900ad2fbee0c343608d422dd1f77bc61c61f4c2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 2655b5a04c..3a7b5d32f0 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -4534,22 +4534,24 @@ There are other requirements beyond the scope of these three and the methods described in this section (e.g. the mechanism through which source code is distributed). + + + As different organizations have different methods of complying with open source licensing, this section is not meant to imply that there is only one single way to meet your compliance obligations, but rather to describe one method of achieving compliance. - - - The remainder of this section describes methods supported to meet the previously mentioned three requirements. Once you take steps to meet these requirements, and prior to releasing images, sources, and the build system, you should audit all artifacts to ensure completeness. - The Yocto Project generates a license manifest during - image creation that is located - in ${DEPLOY_DIR}/licenses/<image_name-datestamp> - to assist with any audits. + + The Yocto Project generates a license manifest during + image creation that is located + in ${DEPLOY_DIR}/licenses/<image_name-datestamp> + to assist with any audits. +
-- cgit v1.2.3-54-g00ecf