documentation: dev-manual - edits to the compliance section.

Feedback from Paul Eggleton suggested to not use the linked
term "Source Directory" in the last paragraph of this section.
Reasoning being that it is mis-leading in this case. People
reading this will be thinking more along the lines of traditional
source code rather than our establishe "Source Directory" term,
which in the doc set refers to either the unpacked poky tarball
or the cloned poky Git repository.

Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: f9bfcdebf85481839df01442ee81c4c9e8ee559a)

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 2012-10-16 06:47:16 -07:00 committed by Richard Purdie
parent aab60fad6d
commit b0c10abb60
1 changed files with 3 additions and 3 deletions

View File

@ -2831,9 +2831,9 @@
##COREBASE##/meta-my-software-layer \
"
</literallayout>
Creating and providing an archive of the
<link linkend='source-directory'>Source Directory</link>
(e.g. <filename>poky</filename>) ensures that you have met your
Creating and providing an archive of the metadata layer
(recipes, configuration files, and so forth)
ensures that you have met your
requirements to include the scripts to control compilation
as well as any modifications to the original source.
</para>