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 <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
13dcc7835f
commit
4c00602eb5
|
@ -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).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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 <filename>${DEPLOY_DIR}/licenses/<image_name-datestamp></filename>
|
||||
to assist with any audits.
|
||||
<note>
|
||||
The Yocto Project generates a license manifest during
|
||||
image creation that is located
|
||||
in <filename>${DEPLOY_DIR}/licenses/<image_name-datestamp></filename>
|
||||
to assist with any audits.
|
||||
</note>
|
||||
</para>
|
||||
|
||||
<section id='providing-the-source-code'>
|
||||
|
|
Loading…
Reference in New Issue