ref-manual: Applied review updates to 2.0 migration section.

Some minor rewordings

(From yocto-docs rev: c62d39ad684c6be3321d711bd7935799e4269fa3)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2015-10-27 08:53:43 -07:00
committed by Richard Purdie
parent a0791c19db
commit e03b19b463

View File

@@ -2642,12 +2642,12 @@
The following QA checks have been added: The following QA checks have been added:
<itemizedlist> <itemizedlist>
<listitem><para> <listitem><para>
Added a "host-user-contaminated" check for any paths Added a "host-user-contaminated" check for ownership
of packaged files outside of issues for packaged files outside of
<filename>/home</filename> that are owned by the user <filename>/home</filename>.
and run BitBake. The check looks for files that are incorrectly owned by the
The existence of these types of paths usually user that ran BitBake instead of owned by a valid user in
indicates ownership has been incorrectly set. the target system.
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
Added an "invalid-chars" check for invalid (non-UTF8) Added an "invalid-chars" check for invalid (non-UTF8)
@@ -2658,10 +2658,11 @@
<link linkend='var-LICENSE'><filename>LICENSE</filename></link>, <link linkend='var-LICENSE'><filename>LICENSE</filename></link>,
and and
<link linkend='var-SECTION'><filename>SECTION</filename></link>). <link linkend='var-SECTION'><filename>SECTION</filename></link>).
Some package managers do not support these variables. Some package managers do not support these characters.
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
Added a check for any options specified in Added an "invalid-packageconfig" check for any options
specified in
<link linkend='var-PACKAGECONFIG'><filename>PACKAGECONFIG</filename></link> <link linkend='var-PACKAGECONFIG'><filename>PACKAGECONFIG</filename></link>
that do not match any <filename>PACKAGECONFIG</filename> that do not match any <filename>PACKAGECONFIG</filename>
option defined for the recipe. option defined for the recipe.