summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-03 09:12:49 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-04 14:13:46 +0100
commit56ce44aa805389427bb4d6fd02a49e53d7a33cad (patch)
treedea9ebbd463e3ed0b2c580056b70e1e2fa8393a0 /documentation
parent6f6d0a59e3b6b8a75522d2918b98de735718f425 (diff)
downloadpoky-56ce44aa805389427bb4d6fd02a49e53d7a33cad.tar.gz
dev-manual: merged "updating images" into the "working with packages"
The section that talked about IPK-specific information for installing updated packages onto an existing running target system is parse and really needs to be in the section that talks about setting up a package repository. I moved it to the end of that repo section. (From yocto-docs rev: 3b1c5858527cba908a5acff1ddc924630cc954b0) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml33
1 files changed, 15 insertions, 18 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index d65d73d59d..43dc61fb24 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2075,24 +2075,6 @@
2075 </section> 2075 </section>
2076 </section> 2076 </section>
2077 2077
2078 <section id="usingpoky-changes-updatingimages">
2079 <title>Updating Existing Images</title>
2080
2081 <para>
2082 Often, rather than re-flashing a new image, you might wish to install updated
2083 packages into an existing running system.
2084 You can do this by first sharing the <filename>tmp/deploy/ipk/</filename> directory
2085 through a web server and then by changing <filename>/etc/opkg/base-feeds.conf</filename>
2086 to point at the shared server.
2087 Following is an example:
2088 <literallayout class='monospaced'>
2089 $ src/gz all http://www.mysite.com/somedir/deploy/ipk/all
2090 $ src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a
2091 $ src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard
2092 </literallayout>
2093 </para>
2094 </section>
2095
2096 <section id='creating-your-own-distribution'> 2078 <section id='creating-your-own-distribution'>
2097 <title>Creating Your Own Distribution</title> 2079 <title>Creating Your Own Distribution</title>
2098 2080
@@ -3213,6 +3195,21 @@
3213 reboot the target device to take advantage of runtime package 3195 reboot the target device to take advantage of runtime package
3214 installations. 3196 installations.
3215 </para> 3197 </para>
3198
3199 <para>
3200 If your packages are IPK, you can install packages onto an
3201 existing running system by first sharing the
3202 <filename>tmp/deploy/ipk/</filename> directory
3203 through a web server and then by changing
3204 <filename>/etc/opkg/base-feeds.conf</filename>
3205 to point at the shared server.
3206 Following is an example:
3207 <literallayout class='monospaced'>
3208 $ src/gz all http://www.mysite.com/somedir/deploy/ipk/all
3209 $ src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a
3210 $ src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard
3211 </literallayout>
3212 </para>
3216 </section> 3213 </section>
3217 </section> 3214 </section>
3218 3215