sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Read-thru edits for "Maintaining Open Source License..." 

A few minor edits.

(From yocto-docs rev: 6051ad964bda3ba78ea3a75199fda87133cc08fd)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-03-19 08:37:38 -06:00 committed by Richard Purdie
parent c70b6e8a42
commit e8c60977c6
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -6751,8 +6751,9 @@
With hundreds of different open source licenses that the Yocto
Project tracks, it is difficult to know the requirements of each
and every license.
However, we can begin to cover the requirements of the major FLOSS licenses, by
assuming that there are three main areas of concern:
However, the requirements of the major FLOSS licenses can begin
to be covered by
assuming that three main areas of concern exist:
<itemizedlist>
<listitem><para>Source code must be provided.</para></listitem>
<listitem><para>License text for the software must be
@ -6813,7 +6814,7 @@
The Yocto Project provides an archiver class to help avoid
some of these concerns.
See the
"<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-archiver'>Archiving Sources - <filename>archive*.bbclass</filename></ulink>"
"<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-archiver'><filename>archive*.bbclass</filename></ulink>"
section in the Yocto Project Reference Manual for information
on this class.
</para>
@ -6851,7 +6852,7 @@
A way to help mitigate the size issue is to only release
tarballs for licenses that require the release of
source.
Let's assume you are only concerned with GPL code as
Let us assume you are only concerned with GPL code as
identified with the following:
<literallayout class='monospaced'>
$ cd poky/build/tmp/deploy/sources
@ -6916,7 +6917,7 @@
and a distro layer, and those those layers are used to patch,
compile, package, or modify (in any way) any open source
software included in your released images, you
may be required to to release those layers under section 3 of
might be required to to release those layers under section 3 of
GPLv2 or section 1 of GPLv3.
One way of doing that is with a clean
checkout of the version of the Yocto Project and layers used