]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commitdiff
dev-manual: Created tip for using server outside of build area
authorScott Rifenbark <srifenbark@gmail.com>
Tue, 20 Mar 2018 19:16:55 +0000 (12:16 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 25 Mar 2018 08:41:12 +0000 (09:41 +0100)
Fixes [YOCTO #12419]

In the section on runtime package management, I created a "Tip"
box to tell the user about using a location for the package
index information outside of the "deploy" area of the hosts
build directory.

(From yocto-docs rev: 2aee814d3d3ed4052fca332693d5416907ae640e)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
documentation/dev-manual/dev-manual-common-tasks.xml

index 6bb42752672f975644265bc5f43e2f41f59ade9a..20f97b9f86e93ec46d458623f48795dc895eddc1 100644 (file)
@@ -9184,12 +9184,17 @@ Some notes from Cal:
                         The critical requirement is that the URIs in the
                         target repository configuration point to the
                         correct remote location for the feeds.
-                        This example uses a location outside of the build
-                        system's <filename>deploy</filename> directory.
-                        Realize that it is possible to run a web server
-                        that gets the databases from
-                        <filename>deploy</filename> directory where the image
-                        was built.
+                        <note><title>Tip</title>
+                            For development purposes, you can point the web
+                            server to the build system's
+                            <filename>deploy</filename> directory.
+                            However, for production use, it is better to copy
+                            the package directories to a location outside of
+                            the build area and use that location.
+                            Doing so avoids situations where the build system
+                            overwrites or changes the
+                            <filename>deploy</filename> directory.
+                        </note>
                     </para>
 
                     <para>