summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-06-07 15:59:53 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-06-21 12:59:07 +0100
commit508e8908c20f65b797c93895cec44b496380fcd9 (patch)
tree70b7bb3a1af3719407c3d63333119bd0fc8911d4 /documentation
parentcd7f7871749283b5220161521b8bed8e3ef5b29a (diff)
downloadopenembedded-core-contrib-508e8908c20f65b797c93895cec44b496380fcd9.tar.gz
openembedded-core-contrib-508e8908c20f65b797c93895cec44b496380fcd9.tar.bz2
openembedded-core-contrib-508e8908c20f65b797c93895cec44b496380fcd9.zip
dev-manual: Review edits applied to the package feed build considerations.
(From yocto-docs rev: 0810f8272be51219d03b06d6771a35bbe6d6e552) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml37
1 files changed, 9 insertions, 28 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 24a7bdc28a..6e0a618277 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -7799,8 +7799,6 @@
<para>
The <filename>smart</filename> application performs
runtime package management of RPM packages.
- This application is aware of every package database
- you want to use.
You must perform an initial setup for
<filename>smart</filename> on the target machine.
</para>
@@ -7835,8 +7833,6 @@
<para>
The <filename>opkg</filename> application performs
runtime package management of IPK packages.
- This application is aware of every package database
- you want to use.
You must perform an initial setup for
<filename>opkg</filename> on the target machine.
</para>
@@ -7852,25 +7848,12 @@
</para>
<para>
- For example, assume the following:
- <itemizedlist>
- <listitem><para>
- An HTTP server named
- <filename>my.server</filename> exists on your
- build machine.
- </para></listitem>
- <listitem><para>
- The server is serving packages from a directory
- named <filename>ipk/</filename>.
- </para></listitem>
- <listitem><para>
- The target machine is able to use the
- <filename>i586</filename>,
- <filename>all</filename>, and
- <filename>qemux86</filename> package
- databases.
- </para></listitem>
- </itemizedlist>
+ As an example, suppose you are serving packages from a
+ <filename>ipk/</filename> directory containing the
+ <filename>i586</filename>,
+ <filename>all</filename>, and
+ <filename>qemux86</filename> databases through an
+ HTTP server named <filename>my.server</filename>.
On the target, create a configuration file
(e.g. <filename>my_repo.conf</filename>) inside the
<filename>/etc/opkg/</filename> directory containing
@@ -7883,7 +7866,7 @@
Next, instruct <filename>opkg</filename> to fetch
the repository information:
<literallayout class='monospaced'>
- #opkg update
+ # opkg update
</literallayout>
The <filename>opkg</filename> application is now able
to find, install, and upgrade packages from the
@@ -7899,10 +7882,8 @@
runtime package management of DEB packages.
This application uses a source list file to find
available package databases.
- The application is aware of every package database
- you want to use.
You must perform an initial setup for
- <filename>opkg</filename> on the target machine.
+ <filename>apt</filename> on the target machine.
</para>
<para>
@@ -7926,7 +7907,7 @@
Next, instruct the <filename>apt</filename>
application to fetch the repository information:
<literallayout class='monospaced'>
- #apt-get update
+ # apt-get update
</literallayout>
After this step, <filename>apt</filename> is able
to find, install, and upgrade packages from the