diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index e2e89a032c..e161c7265e 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3996,31 +3996,19 @@
As a way of making it easier to generate and make
these IPK configuration files available on your
- target, the meta-oe layer
- provides a recipe called
- distro-feed-configs, which
- provides a package by the same name.
- When you include this package into your image, it will
- automatically generate and include a set of
- *.conf files in the image's
- /etc/opkg directory that will
- provide your target's opkg
- tool with any and all package databases your build will
- generate.
- The only catch is that this recipe cannot possibly
- imagine your server's DNS name/IP address.
- Consequently, somewhere in your configuration you need
- to set a variable called
- DISTRO_FEED_URI to point
+ target, simply define
+ FEED_DEPLOYDIR_BASE_URI to point
to your server and the location within the
- document-root that contains the databases.
- For example: if you are serving your packages over HTTP,
- your server's IP address is 192.168.7.1, and your
- databases are located in a directory called
+ document-root which contains the databases.
+ For example: if you are serving your packages over
+ HTTP, your server's IP address is 192.168.7.1, and
+ your databases are located in a directory called
BOARD-dir underneath your HTTP
server's document-root, you need to set
- DISTRO_FEED_URI to
- http://192.168.7.1/BOARD-dir.
+ FEED_DEPLOYDIR_BASE_URI to
+ http://192.168.7.1/BOARD-dir and
+ a set of configuration files will be generated for you
+ in your target to work with this feed.