ref-manual, mega-manual: Added manifest file information

Fixes [YOCTO #5410]

I updated the figure that shows what do_rootfs does to create
the image.  The new addition is the creation of the .manifest file
that lists out package information in the image.  Supporting text
was also added in the section.

The updated figure was needed in both the ref-manual and
mega-manual figures folders.

Also, part of the fix included a new variable description for the
IMAGE_MANIFEST variable.

(From yocto-docs rev: 770448e0e8ce2e2c517ced5e71f5a916fefe5cf2)

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

1 files changed, 33 insertions, 0 deletions

diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 033661af1c..5f2b76be8c 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -2903,6 +2903,39 @@
             </glossdef>
         </glossentry>
 
+        <glossentry id='var-IMAGE_MANIFEST'><glossterm>IMAGE_MANIFEST</glossterm>
+            <glossdef>
+                <para>
+                    The manifest file for the image.
+                    This file lists all the installed packages that make up
+                    the image.
+                    The file contains package information on a line-per-package
+                    basis as follows:
+                    <literallayout class='monospaced'>
+     &lt;packagename&gt; &lt;packagearch&gt; &lt;version&gt;
+                    </literallayout>
+                </para>
+
+                <para>
+                    The
+                    <link linkend='ref-classes-image'><filename>image</filename></link>
+                    class defines the manifest file as follows:
+                    <literallayout class='monospaced'>
+     IMAGE_MANIFEST = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.manifest"
+                    </literallayout>
+                    The location is derived using the
+                    <link linkend='var-DEPLOY_DIR_IMAGE'><filename>DEPLOY_DIR_IMAGE</filename></link>
+                    and
+                    <link linkend='var-IMAGE_NAME'><filename>IMAGE_NAME</filename></link>
+                    variables.
+                    You can find information on how the image
+                    is created in the
+                    "<link linkend='image-generation-dev-environment'>Image Generation</link>"
+                    section.
+                </para>
+            </glossdef>
+        </glossentry>
+
         <glossentry id='var-IMAGE_NAME'><glossterm>IMAGE_NAME</glossterm>
             <glossdef>
                 <para>