From 0c4b95531cb83826770a12c3ee66c3e628992004 Mon Sep 17 00:00:00 2001
From: Trevor Woerner <trevor.woerner@linaro.org>
Date: Tue, 5 Nov 2013 09:32:22 -0800
Subject: [PATCH] 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: 0f6d955c5d7fba7258441ce6dbdecfac67d722f7)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../dev-manual/dev-manual-common-tasks.xml    | 32 ++++++-------------
 1 file 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 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 @@
                     <para>
                         As a way of making it easier to generate and make
                         these IPK configuration files available on your
-                        target, the <filename>meta-oe</filename> layer
-                        provides a recipe called
-                        <filename>distro-feed-configs</filename>, 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
-                        <filename>*.conf</filename> files in the image's
-                        <filename>/etc/opkg</filename> directory that will
-                        provide your target's <filename>opkg</filename>
-                        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
-                        <filename>DISTRO_FEED_URI</filename> to point
+                        target, simply define
+                        <filename>FEED_DEPLOYDIR_BASE_URI</filename> 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
                         <filename>BOARD-dir</filename> underneath your HTTP
                         server's document-root, you need to set
-                        <filename>DISTRO_FEED_URI</filename> to
-                        <filename>http://192.168.7.1/BOARD-dir</filename>.
+                        <filename>FEED_DEPLOYDIR_BASE_URI</filename> to
+                        <filename>http://192.168.7.1/BOARD-dir</filename> and
+                        a set of configuration files will be generated for you
+                        in your target to work with this feed.
                     </para>
 
                     <para>