ref-manual, dev-manual: Review comments applied to package repository

Changes are the review comments from Paul Eggleton regarding
setting up the optional package repository on the host that
can be used by Smart.  These changes reflect the fact that
the task is not package-type dependent or host web server
dependent.

(From yocto-docs rev: 779989878bcc9501ddc4570519d93325442a8493)

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 2013-04-03 08:04:31 -07:00 committed by Richard Purdie
parent c683dfb38f
commit 9a98f403bd
2 changed files with 100 additions and 108 deletions

View File

@ -3126,7 +3126,8 @@
<title>Setting Up Runtime Package Management</title>
<para>
It is possible to set up a repository that is a host-based
For RPM, IPK, and DEB package formats, it is possible to set
up a repository that is a host-based
package feed from which you can install packages on the
target system during runtime.
Doing so is optional and depends on the following:
@ -3136,13 +3137,13 @@
</para></listitem>
<listitem><para>
When you build your image, you select to use the
RPM package manager by setting the
appropriate package manager by setting the
<ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink>
variable.
</para></listitem>
<listitem><para>
You have Apache 2 installed and configured on the
development host.
You have a supported web server, such as Apache 2,
installed and configured on the development host.
</para></listitem>
<listitem><para>
You have <filename>createrepo</filename> installed on
@ -3152,7 +3153,9 @@
</para>
<para>
Here are the steps to set up this optional package feed:
Following are the steps to set up the optional repository.
This examples assumes you are using RPM and the Apache 2
server:
<orderedlist>
<listitem><para>
Add the directory to your Apache configuration, which
@ -3179,18 +3182,6 @@
<para>
If your development system is using Fedora or
CentOS, use the following:
</para>
<note>
<emphasis>Note to Self:</emphasis> Paul says that
some of the distros (Fedora and CentOS in
particular) might have different commands based
on the distro version.
We need links for the reader to follow for the
specifics.
We don't want to have to document all this
distro-specific stuff.
</note>
<para>
<literallayout class='monospaced'>
service httpd reload
</literallayout>

View File

@ -327,6 +327,16 @@
The first class listed in this variable is used for image generation.
</para>
<para>
If you take the optional step to set up a repository (package feed)
on the development host that can be used by Smart, you can
install packages from the feed while you are running the image
on the target (i.e. runtime installation of packages).
For information on how to set up this repository, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#setting-up-runtime-package-management'>Setting Up Runtime Package Management</ulink>"
in the Yocto Project Development Manual.
</para>
<para>
The package class you choose can affect build-time performance and has space
ramifications.
@ -359,15 +369,6 @@
Database and the amount of metadata when using RPM can affect
your ability to perform on-device upgrades.
</para></listitem>
<listitem><para>
If you take the steps to set up a repository (package feed)
on the development host that can be used by Smart, you can
install packages from the feed while you are running the image
on the target (i.e. runtime installation of packages).
For information on how to set up this repository, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#setting-up-runtime-package-management'>Setting Up Runtime Package Management</ulink>"
in the Yocto Project Development Manual.
</para></listitem>
</itemizedlist>
</para>