Documentation: poky-ref-manual - Removed all trailing whitespace.

(From yocto-docs rev: 564a28c2501034ea7e2eb16afc43dfaf931b6f6f)

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

1 files changed, 74 insertions, 74 deletions

diff --git a/documentation/poky-ref-manual/migration.xml b/documentation/poky-ref-manual/migration.xml
index b311da65c5..40c570f8ca 100644
--- a/documentation/poky-ref-manual/migration.xml
+++ b/documentation/poky-ref-manual/migration.xml
@@ -6,8 +6,8 @@
 <title>Migrating to a Newer Yocto Project Release</title>
 
     <para>
-        This chapter provides information you can use to migrate work to a 
-        newer Yocto Project release.  You can find the same information in the 
+        This chapter provides information you can use to migrate work to a
+        newer Yocto Project release.  You can find the same information in the
         release notes for a given release.
     </para>
 
@@ -15,7 +15,7 @@
     <title>Moving to the Yocto Project 1.3 Release</title>
 
     <para>
-        This section provides migration information for moving to the 
+        This section provides migration information for moving to the
         Yocto Project 1.3 Release.
     </para>
 
@@ -23,7 +23,7 @@
         <title>Local Configuration</title>
 
         <para>
-            Differences include changes for 
+            Differences include changes for
             <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link>
             and <filename>bblayers.conf</filename>.
         </para>
@@ -32,18 +32,18 @@
             <title>SSTATE_MIRRORS</title>
 
             <para>
-                The shared state cache (sstate-cache) as pointed to by 
-                <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link> by default 
-                now has two-character subdirectories to prevent there being an issue with too 
+                The shared state cache (sstate-cache) as pointed to by
+                <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link> by default
+                now has two-character subdirectories to prevent there being an issue with too
                 many files in the same directory.
-                Also, native sstate-cache packages will go into a subdirectory named using 
-                the distro ID string. 
-                If you copy the newly structured sstate-cache to a mirror location 
-                (either local or remote) and then point to it in 
+                Also, native sstate-cache packages will go into a subdirectory named using
+                the distro ID string.
+                If you copy the newly structured sstate-cache to a mirror location
+                (either local or remote) and then point to it in
                 <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link>,
-                you need to append "PATH" to the end of the mirror URL so that 
-                the path used by BitBake before the mirror substitution is 
-                appended to the path used to access the mirror. 
+                you need to append "PATH" to the end of the mirror URL so that
+                the path used by BitBake before the mirror substitution is
+                appended to the path used to access the mirror.
                 Here is an example:
                 <literallayout class='monospaced'>
      SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH"
@@ -55,14 +55,14 @@
             <title>bblayers.conf</title>
 
             <para>
-                The <filename>meta-yocto</filename> layer has been split into 
-                two parts: <filename>meta-yocto</filename> and 
-                <filename>meta-yocto-bsp</filename>, corresponding to the 
+                The <filename>meta-yocto</filename> layer has been split into
+                two parts: <filename>meta-yocto</filename> and
+                <filename>meta-yocto-bsp</filename>, corresponding to the
                 Poky reference distro configuration and the reference
-                hardware Board Support Packages (BSPs), respectively. 
-                When running BitBake or Hob for the first time after upgrading, 
-                your <filename>conf/bblayers.conf</filename> file will be 
-                updated to handle this change and you will be asked to 
+                hardware Board Support Packages (BSPs), respectively.
+                When running BitBake or Hob for the first time after upgrading,
+                your <filename>conf/bblayers.conf</filename> file will be
+                updated to handle this change and you will be asked to
                 re-run/restart for the changes to take effect.
             </para>
         </section>
@@ -87,16 +87,16 @@
             <title>Python Function Whitespace</title>
 
             <para>
-                All Python functions must now use four spaces for indentation. 
+                All Python functions must now use four spaces for indentation.
                 Previously, an inconsistent mix of spaces and tabs existed,
-                which made extending these functions using 
+                which made extending these functions using
                 <filename>_append</filename> or <filename>_prepend</filename>
-                complicated given that Python treats whitespace as 
-                syntactically significant. 
+                complicated given that Python treats whitespace as
+                syntactically significant.
                 If you are defining or extending any Python functions (e.g.
                 <filename>populate_packages</filename>, <filename>do_unpack</filename>,
                 <filename>do_patch</filename> and so forth) in custom recipes
-                or classes, you need to ensure you are using consistent 
+                or classes, you need to ensure you are using consistent
                 four-space indentation.
             </para>
         </section>
@@ -105,7 +105,7 @@
             <title>proto= in SRC_URI</title>
 
             <para>
-                Any use of <filename>proto=</filename> in 
+                Any use of <filename>proto=</filename> in
                 <link linkend='var-SRC_URI'><filename>SRC_URI</filename></link>
                 needs to be changed to <filename>protocol=</filename>.
                 In particular, this applies to the following URIs:
@@ -125,11 +125,11 @@
 
             <para>
                 The suffix <filename>nativesdk</filename> is now implemented
-                as a prefix, which simplifies a lot of the packaging code for 
-                <filename>nativesdk</filename> recipes. 
-                All custom <filename>nativesdk</filename> recipes and any 
-                references need to be updated to use 
-                <filename>nativesdk-*</filename> instead of 
+                as a prefix, which simplifies a lot of the packaging code for
+                <filename>nativesdk</filename> recipes.
+                All custom <filename>nativesdk</filename> recipes and any
+                references need to be updated to use
+                <filename>nativesdk-*</filename> instead of
                 <filename>*-nativesdk</filename>.
             </para>
         </section>
@@ -138,25 +138,25 @@
             <title>Task Recipes</title>
 
             <para>
-                "Task" recipes are now known as "Package groups" and have 
-                been renamed from <filename>task-*.bb</filename> to 
-                <filename>packagegroup-*.bb</filename>. 
+                "Task" recipes are now known as "Package groups" and have
+                been renamed from <filename>task-*.bb</filename> to
+                <filename>packagegroup-*.bb</filename>.
                 Existing references to the previous <filename>task-*</filename>
-                names should work in most cases as there is an automatic 
+                names should work in most cases as there is an automatic
                 upgrade path for most packages.
-                However, you should update references in your own recipes and 
-                configurations as they could be removed in future releases. 
+                However, you should update references in your own recipes and
+                configurations as they could be removed in future releases.
                 You should also rename any custom <filename>task-*</filename>
-                recipes to <filename>packagegroup-*</filename>, and change 
-                them to inherit <filename>packagegroup</filename> instead of 
-                <filename>task</filename>, as well as taking the opportunity 
-                to remove anything now handled by 
+                recipes to <filename>packagegroup-*</filename>, and change
+                them to inherit <filename>packagegroup</filename> instead of
+                <filename>task</filename>, as well as taking the opportunity
+                to remove anything now handled by
                 <filename>packagegroup.bbclass</filename>, such as providing
                 <filename>-dev</filename> and <filename>-dbg</filename>
-                packages, setting 
-                <link linkend='var-LIC_FILES_CHKSUM'><filename>LIC_FILES_CHKSUM</filename></link>, 
+                packages, setting
+                <link linkend='var-LIC_FILES_CHKSUM'><filename>LIC_FILES_CHKSUM</filename></link>,
                 and so forth.
-                See the 
+                See the
                 "<link linkend='ref-classes-packagegroup'>Package Groups - packagegroup.bbclass</link>"
                 section for further details.
             </para>
@@ -166,13 +166,13 @@
             <title>IMAGE_FEATURES</title>
 
             <para>
-                Image recipes that previously included "apps-console-core" 
+                Image recipes that previously included "apps-console-core"
                 in <link linkend='var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></link>
-                should now include "splash" instead to enable the boot-up 
+                should now include "splash" instead to enable the boot-up
                 splash screen.
-                Retaining "apps-console-core" will still include the splash 
+                Retaining "apps-console-core" will still include the splash
                 screen generates a warning.
-                The "apps-x11-core" and "apps-x11-games" 
+                The "apps-x11-core" and "apps-x11-games"
                 <filename>IMAGE_FEATURES</filename> features have been removed.
             </para>
         </section>
@@ -181,55 +181,55 @@
             <title>Removed Recipes</title>
 
             <para>
-                The following recipes have been removed. 
-                For most of them, it is unlikely that you would have any 
+                The following recipes have been removed.
+                For most of them, it is unlikely that you would have any
                 references to them in your own metadata.
                 However, you should check your metadata against this list to be sure:
                 <itemizedlist>
-                    <listitem><para><emphasis><filename>libx11-trim</filename></emphasis>: 
-                        Replaced by <filename>libx11</filename>, which has a negligible 
+                    <listitem><para><emphasis><filename>libx11-trim</filename></emphasis>:
+                        Replaced by <filename>libx11</filename>, which has a negligible
                         size difference with modern Xorg.</para></listitem>
-                    <listitem><para><emphasis><filename>xserver-xorg-lite</filename></emphasis>: 
-                        Use <filename>xserver-xorg</filename>, which has a negligible 
+                    <listitem><para><emphasis><filename>xserver-xorg-lite</filename></emphasis>:
+                        Use <filename>xserver-xorg</filename>, which has a negligible
                         size difference when DRI and GLX modules are not installed.</para></listitem>
-                    <listitem><para><emphasis><filename>xserver-kdrive</filename></emphasis>: 
+                    <listitem><para><emphasis><filename>xserver-kdrive</filename></emphasis>:
                         Effectively unmaintained for many years.</para></listitem>
-                    <listitem><para><emphasis><filename>mesa-xlib</filename></emphasis>: 
+                    <listitem><para><emphasis><filename>mesa-xlib</filename></emphasis>:
                         No longer serves any purpose.</para></listitem>
-                    <listitem><para><emphasis><filename>galago</filename></emphasis>: 
+                    <listitem><para><emphasis><filename>galago</filename></emphasis>:
                         Replaced by telepathy.</para></listitem>
-                    <listitem><para><emphasis><filename>gail</filename></emphasis>: 
+                    <listitem><para><emphasis><filename>gail</filename></emphasis>:
                         Functionality was integrated into GTK+ 2.13.</para></listitem>
-                    <listitem><para><emphasis><filename>eggdbus</filename></emphasis>: 
+                    <listitem><para><emphasis><filename>eggdbus</filename></emphasis>:
                         No longer needed.</para></listitem>
-                    <listitem><para><emphasis><filename>gcc-*-intermediate</filename></emphasis>: 
-                        The build has been restructured to avoid the need for 
+                    <listitem><para><emphasis><filename>gcc-*-intermediate</filename></emphasis>:
+                        The build has been restructured to avoid the need for
                         this step.</para></listitem>
-                    <listitem><para><emphasis><filename>libgsmd</filename></emphasis>: 
+                    <listitem><para><emphasis><filename>libgsmd</filename></emphasis>:
                         Unmaintained for many years.
-                        Functionality now provided by 
+                        Functionality now provided by
                         <filename>ofono</filename> instead.</para></listitem>
-                    <listitem><para><emphasis>contacts, dates, tasks, eds-tools</emphasis>: 
+                    <listitem><para><emphasis>contacts, dates, tasks, eds-tools</emphasis>:
                         Largely unmaintained PIM application suite.
                         It has been moved to <filename>meta-gnome</filename>
                         in <filename>meta-openembedded</filename>.</para></listitem>
                 </itemizedlist>
-                In addition to the previously listed changes, the 
+                In addition to the previously listed changes, the
                 <filename>meta-demoapps</filename> directory has also been removed
-                because the recipes in it were not being maintained and many 
+                because the recipes in it were not being maintained and many
                 had become obsolete or broken.
                 Additionally, these recipes were not parsed in the default configuration.
-                Many of these recipes are already provided in an updated and 
-                maintained form within OpenEmbedded community layers such as 
+                Many of these recipes are already provided in an updated and
+                maintained form within OpenEmbedded community layers such as
                 <filename>meta-oe</filename> and <filename>meta-gnome</filename>.
-                For the remainder, you can now find them in the 
-                <filename>meta-extras</filename> repository, which is in the 
+                For the remainder, you can now find them in the
+                <filename>meta-extras</filename> repository, which is in the
                 Yocto Project source repositories.
             </para>
-        </section>        
+        </section>
     </section>
 </section>
 </chapter>
-<!-- 
-vim: expandtab tw=80 ts=4 
+<!--
+vim: expandtab tw=80 ts=4
 -->