[FE training-materials-updates] Add details about repo manifests

Maxime Ripard maxime.ripard at free-electrons.com
Wed Apr 16 17:44:02 CEST 2014


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

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

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

commit f2b26264ff5c20ee694ec0ac4fdee0fb180f6c32
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Wed Apr 16 16:22:58 2014 +0200

    Add details about repo manifests
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

f2b26264ff5c20ee694ec0ac4fdee0fb180f6c32
 .../android-source-obtaining.tex                   |   53 ++++++++++++++++----
 1 file changed, 42 insertions(+), 11 deletions(-)

diff --git a/slides/android-source-obtaining/android-source-obtaining.tex b/slides/android-source-obtaining/android-source-obtaining.tex
index fdc0541..e38a1d4 100644
--- a/slides/android-source-obtaining/android-source-obtaining.tex
+++ b/slides/android-source-obtaining/android-source-obtaining.tex
@@ -18,6 +18,22 @@
 \end{frame}
 
 \begin{frame}
+  \frametitle{Source code licenses}
+  \begin{itemize}
+  \item Mostly two kind of licenses:
+    \begin{itemize}
+    \item GPL/LGPL Code: Linux
+    \item Apache/BSD: All the rest
+    \item In the \code{external} folder, it depends on the component
+    \end{itemize}
+  \item While you might expect Google's apps for Android, like the
+    Android Market (now called Google Play Store), to be in the AOSP
+    as well, these are actually proprietary and you need to be
+    approved by Google to get them.
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
   \frametitle{Repo}
   \begin{itemize}
   \item This makes hundreds of Git repositories\!
@@ -34,17 +50,32 @@
 \end{frame}
 
 \begin{frame}
-  \frametitle{Source code licenses}
+  \frametitle{Repo's manifest}
   \begin{itemize}
-  \item Mostly two kind of licenses:
-    \begin{itemize}
-    \item GPL/LGPL Code: Linux
-    \item Apache/BSD: All the rest
-    \item In the \code{external} folder, it depends on the component
-    \end{itemize}
-  \item While you might expect Google's apps for Android, like the
-    Android Market (now called Google Play Store), to be in the AOSP
-    as well, these are actually proprietary and you need to be
-    approved by Google to get them.
+  \item \code{repo} relies on a git repository that will contain XML
+    files called manifests
+  \item These manifests gives the information about where to download
+    some source code and where to store it. It can also provide some
+    additional and optional informations such as a revision to use, an
+    alternative server to download from, etc.
+  \item The main manifests are stored in this git repo, and are shared
+    between all the users, but you can add some local manifests.
+  \item \code{repo} will also use any XML file that is under
+    \code{.repo/local_manifests}
   \end{itemize}
 \end{frame}
+
+\begin{frame}[fragile]
+  \frametitle{Manifests syntax}
+\begin{minted}[fontsize=\scriptsize]{xml}
+<?xml version="1.0" encoding="UTF-8"?>
+<manifest>
+  <remote name="github"
+          fetch="https://github.com/" />
+
+  <default remote="github" />
+
+  <project name="foo/bar" path="device/foo/bar" revision="v14.42" />
+</manifest>
+\end{minted}
+\end{frame}
\ No newline at end of file



More information about the training-materials-updates mailing list