documentation/poky-ref-manual/ref-structure.xml: deleting images

Added clarification on how a user can hand-delete images from
the build/tmp/deply/images directory.

(From yocto-docs rev: 4655085d43b36b024a2e01cfcc7455e18d891ab8)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 19 insertions, 6 deletions

diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index 8f705537c4..2db58ddaef 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -329,14 +329,27 @@
             This directory receives complete filesystem images. 
             If you want to flash the resulting image from a build onto a device, look here for the image.
         </para>
- 
+
+        <para>
+            Be careful when deleting files in this directory. 
+            You can safely delete old images from this directory (e.g. 
+            <filename>core-image-*</filename>, <filename>hob-image-*</filename>,
+            etc.). 
+            However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.), 
+            bootloader and other supplementary files might be deployed here prior to building an
+            image.
+            Because these files, however, are not directly produced from the image, if you
+            delete them they will not be automatically re-created when you build the image again.
+        </para>
+
         <para>
-            Note, you should not remove any files from this directory by hand in an attempt
-            to rebuild an image. 
-            If you want to clean out the cache, re-run the build using the following 
-            BitBake command:
+            If you do accidentally delete files here, you will need to force them to be 
+            re-created. 
+            In order to do that, you will need to know the target that produced them.
+            For example, these commands rebuild and re-create the kernel files:
             <literallayout class='monospaced'>
-     $ bitbake -c cleanall &lt;target&gt;
+     $ bitbake -c clean virtual/kernel
+     $ bitbake virtual/kernel
             </literallayout>
         </para>
     </section>