[FE training-materials-updates] yocto: slides: move the dependencies part in the basic recipe chapter

[Antoine Ténart]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=6789348bdd6cb2f0cf39dae6a793f273dd3ac902

>---------------------------------------------------------------

commit 6789348bdd6cb2f0cf39dae6a793f273dd3ac902
Author: Antoine Tenart <antoine.tenart at free-electrons.com>
Date:   Thu Dec 11 12:32:04 2014 +0100

    yocto: slides: move the dependencies part in the basic recipe chapter
    
    Signed-off-by: Antoine Tenart <antoine.tenart at free-electrons.com>


>---------------------------------------------------------------

6789348bdd6cb2f0cf39dae6a793f273dd3ac902
 .../yocto-recipe-advanced.tex                      | 22 ----------------------
 slides/yocto-recipe-basics/yocto-recipe-basics.tex | 21 +++++++++++++++++++++
 2 files changed, 21 insertions(+), 22 deletions(-)

diff --git a/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex b/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
index 9d33eed..ad00ffc 100644
--- a/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
+++ b/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
@@ -95,7 +95,6 @@ SRC_URI += "file://custom-modification-0.patch \
     \item In the real word, more complex configurations are often needed
           because recipes may:
     \begin{itemize}
-      \item Have dependencies
       \item Provide virtual packages
       \item Inherit generic functions from classes
     \end{itemize}
@@ -103,27 +102,6 @@ SRC_URI += "file://custom-modification-0.patch \
 \end{frame}
 
 \begin{frame}
-  \frametitle{Add dependencies}
-  \begin{itemize}
-    \item A package can have dependencies during the build or at
-          runtime. To reflect these requirements in the recipe, two
-          variables are used:
-    \begin{description}
-      \item[DEPENDS] List of the package build-time dependencies.
-      \item[RDEPENDS] List of the package runtime
-        dependencies. Must be package specific (e.g. with
-        \code{_${PN}}).
-    \end{description}
-    \item \code{DEPENDS = "package_b"}: the local \code{do_configure}
-      task depends on the \code{do_populate_sysroot} task of package
-      b.
-    \item \code{RDEPENDS_${PN} = "package_b"}: the local
-      \code{do_build} task depends on the
-      \code{do_package_write_<archive-format>} task of package b.
-  \end{itemize}
-\end{frame}
-
-\begin{frame}
   \frametitle{Providing virtual packages}
   \begin{itemize}
     \item BitBake allows to use virtual names instead of the actual
diff --git a/slides/yocto-recipe-basics/yocto-recipe-basics.tex b/slides/yocto-recipe-basics/yocto-recipe-basics.tex
index e3cd579..db8f4c9 100644
--- a/slides/yocto-recipe-basics/yocto-recipe-basics.tex
+++ b/slides/yocto-recipe-basics/yocto-recipe-basics.tex
@@ -175,6 +175,27 @@
   \end{itemize}
 \end{frame}
 
+\begin{frame}
+  \frametitle{Dependencies}
+  \begin{itemize}
+    \item A package can have dependencies during the build or at
+          runtime. To reflect these requirements in the recipe, two
+          variables are used:
+    \begin{description}
+      \item[DEPENDS] List of the package build-time dependencies.
+      \item[RDEPENDS] List of the package runtime
+        dependencies. Must be package specific (e.g. with
+        \code{_${PN}}).
+    \end{description}
+    \item \code{DEPENDS = "package_b"}: the local \code{do_configure}
+      task depends on the \code{do_populate_sysroot} task of package
+      b.
+    \item \code{RDEPENDS_${PN} = "package_b"}: the local
+      \code{do_build} task depends on the
+      \code{do_package_write_<archive-format>} task of package b.
+  \end{itemize}
+\end{frame}
+
 \begin{frame}[fragile]
   \frametitle{Tasks}
   Default tasks already exists, they are defined in classes: