[FE training-materials-updates] buildroot-advanced-packages: commit progress

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Thu Apr 30 16:57:10 CEST 2015

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

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


commit 4901e8a63618e19b85250a75981dca24257d223e
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu Apr 30 16:57:06 2015 +0200

    buildroot-advanced-packages: commit progress
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


 .../buildroot-advanced-packages.tex                | 79 ++++++++++++++++++++--
 1 file changed, 74 insertions(+), 5 deletions(-)

diff --git a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
index a0ecd3b..50d7c26 100644
--- a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -1,10 +1,79 @@
-\section{Advanced package recipe tricks}
+\section{Advanced package aspects}
-\begin{frame}{Licensing information}
+\begin{frame}[fragile]{Licensing report: introduction}
+  \begin{itemize}
+  \item A key aspect of embedded Linux systems is {\bf license
+      compliance}.
+  \item Embedded Linux systems integrate together a number of
+    open-source components, each distributed under its own license.
+  \item The different open-source licenses may have {\bf different
+      requirements}, that must be met before the product using the
+    embedded Linux system starts shipping.
+  \item Buildroot helps in this license compliance process by offering
+    the possibility of generating a number of {\bf license-related
+      information} from the list of selected packages.
+  \item Generated using:
+$ make legal-info
+  \end{itemize}
+\begin{frame}{Licensing report: contents}
+\begin{frame}{Including licensing information in packages}
+  \begin{itemize}
+  \item \code{<pkg>_LICENSE}
+    \begin{itemize}
+    \item Comma-separated {\bf list of license(s)} under which the
+      package is distributed.
+    \item Free form string, but should use the license codes from
+      \url{https://spdx.org/licenses/}
+    \item Can indicate which part is under which license (programs,
+      tests, libraries, etc.)
+    \end{itemize}
+  \item \code{<pkg>_LICENSE_FILES}
+    \begin{itemize}
+    \item Space-separated {\bf list of file paths} from the package
+      source code containing the license text and copyright
+      information
+    \item Paths relative to the package top-level source directory
+    \end{itemize}
+  \item \code{<pkg>_REDISTRIBUTE}
+    \begin{itemize}
+    \item Boolean indicating whether the package source code should be
+      redistributed or not (part of the \code{legal-info} output)
+    \item Defaults to \code{YES}, can be overriden to \code{NO}
+    \end{itemize}
+  \end{itemize}
+\begin{frame}[fragile]{Licensing information examples}
+  \begin{block}{linux.mk}
+  \end{block}
+ACL_LICENSE = GPLv2+ (programs), LGPLv2.1+ (libraries)

More information about the training-materials-updates mailing list