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

ref-manual: Minor edits for review on new QA checks. 

Fixed some minor issues with build-deps and file-rdeps.

(From yocto-docs rev: b4250c9ba7d6a3d30c3dfb94d9e2e2eea6b47764)

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-10-16 10:44:18 -07:00 committed by Richard Purdie
parent e5255cce86
commit 31d0bb239f
2 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
documentation/ref-manual/ref-classes.xml
View File

@ -1345,7 +1345,8 @@
dependency.
This determination is particularly useful to discover where
runtime dependencies are detected and added during packaging.
At this point in the build it is too late to ensure that
If no explicit dependency has been specified within the
metadata, at the packaging stage it is too late to ensure that
the dependency is built, and thus you can end up with an
error when the package is installed into the image during the
<link linkend='ref-tasks-rootfs'><filename>do_rootfs</filename></link>
@ -1354,7 +1355,7 @@
<link linkend='ref-classes-update-rc.d'><filename>update-rc.d</filename></link>
class automatically adds a dependency on the
<filename>initscripts-functions</filename> package to packages
that install an <filename>initscript</filename> that refers to
that install an initscript that refers to
<filename>/etc/init.d/functions</filename>.
The recipe should really have an explicit
<filename>RDEPENDS</filename> for the package in question on
@ -1415,9 +1416,9 @@
Some very rare cases do exist for dynamically loaded modules where
these symlinks are needed instead in the main package.
</para></listitem>
<listitem><para><emphasis><filename>file-redeps:</filename></emphasis>
<listitem><para><emphasis><filename>file-rdeps:</filename></emphasis>
Checks that file-level dependencies identified by the
OpenEmbedded build system are satisfied.
OpenEmbedded build system at packaging time are satisfied.
For example, a shell script might start with the line
<filename>#!/bin/bash</filename>.
This line would translate to a file dependency on

8
documentation/ref-manual/ref-qa-checks.xml
View File

@ -158,9 +158,9 @@ can be found then it should be implemented. I can't find one at the moment.
<para>
<itemizedlist>
<listitem>
<para id='qa-issue-file->rdeps'>
<para id='qa-issue-file-rdeps'>
<code>
&lt;packagename&gt; requires &lt;files&gt;, but no providers in its RDEPENDS [file->rdeps]
&lt;packagename&gt; requires &lt;files&gt;, but no providers in its RDEPENDS [file-rdeps]
</code>
</para>
@ -171,7 +171,7 @@ can be found then it should be implemented. I can't find one at the moment.
<link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>.
If particular files are required at runtime then
<filename>RDEPENDS</filename> should be declared in the
recipe to ensure they are present.
recipe to ensure the packages providing them are built.
</para>
<para>
@ -186,7 +186,7 @@ can be found then it should be implemented. I can't find one at the moment.
<listitem>
<para id='qa-issue-build-deps'>
<code>
&lt;packagename1&gt; rdepends on &lt;packagename2&gt;, but it isn't a builddependency? [build-deps]
&lt;packagename1&gt; rdepends on &lt;packagename2&gt;, but it isn't a build dependency? [build-deps]
</code>
</para>