summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorTrevor Woerner <trevor.woerner@linaro.org>2013-11-05 09:32:22 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-03 12:53:01 +0000
commitf3c4d68e9e46472208e9c5521ff1a7c8fcbea14d (patch)
treeef4e8313b56d8f158d3a5abb78e78f28f8eff489 /documentation/dev-manual
parentc35d59f1499d65f25a750c8966bc04b26f10232d (diff)
downloadpoky-f3c4d68e9e46472208e9c5521ff1a7c8fcbea14d.tar.gz
dev-manual: package add using facilities in oe-core only.
Fixes [YOCTO #5408] The developer's manual should only refer to functionality which is available in oe-core. Currently, this passage requires the user to add a package from, and use facilities of, meta-oe. This fix describes how to use facilities in oe-core to the same end. (From yocto-docs rev: 2dfaa88ae4760f86dbbdc8b58de7feba25a8014a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml32
1 files changed, 10 insertions, 22 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index cf188aae74..5a4ff3c328 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3996,31 +3996,19 @@
3996 <para> 3996 <para>
3997 As a way of making it easier to generate and make 3997 As a way of making it easier to generate and make
3998 these IPK configuration files available on your 3998 these IPK configuration files available on your
3999 target, the <filename>meta-oe</filename> layer 3999 target, simply define
4000 provides a recipe called 4000 <filename>FEED_DEPLOYDIR_BASE_URI</filename> to point
4001 <filename>distro-feed-configs</filename>, which
4002 provides a package by the same name.
4003 When you include this package into your image, it will
4004 automatically generate and include a set of
4005 <filename>*.conf</filename> files in the image's
4006 <filename>/etc/opkg</filename> directory that will
4007 provide your target's <filename>opkg</filename>
4008 tool with any and all package databases your build will
4009 generate.
4010 The only catch is that this recipe cannot possibly
4011 imagine your server's DNS name/IP address.
4012 Consequently, somewhere in your configuration you need
4013 to set a variable called
4014 <filename>DISTRO_FEED_URI</filename> to point
4015 to your server and the location within the 4001 to your server and the location within the
4016 document-root that contains the databases. 4002 document-root which contains the databases.
4017 For example: if you are serving your packages over HTTP, 4003 For example: if you are serving your packages over
4018 your server's IP address is 192.168.7.1, and your 4004 HTTP, your server's IP address is 192.168.7.1, and
4019 databases are located in a directory called 4005 your databases are located in a directory called
4020 <filename>BOARD-dir</filename> underneath your HTTP 4006 <filename>BOARD-dir</filename> underneath your HTTP
4021 server's document-root, you need to set 4007 server's document-root, you need to set
4022 <filename>DISTRO_FEED_URI</filename> to 4008 <filename>FEED_DEPLOYDIR_BASE_URI</filename> to
4023 <filename>http://192.168.7.1/BOARD-dir</filename>. 4009 <filename>http://192.168.7.1/BOARD-dir</filename> and
4010 a set of configuration files will be generated for you
4011 in your target to work with this feed.
4024 </para> 4012 </para>
4025 4013
4026 <para> 4014 <para>