[bootlin/training-materials updates] master: labs/buildroot-new-packages: add sanity checking step (3cf23fd8)

[Thomas Petazzoni]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/3cf23fd832c3f455b1a9ca60981c8e09c73ae73d

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

commit 3cf23fd832c3f455b1a9ca60981c8e09c73ae73d
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Wed Mar 20 11:15:01 2019 +0100

    labs/buildroot-new-packages: add sanity checking step
    
    Make use of the new "check-package" make target.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


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

3cf23fd832c3f455b1a9ca60981c8e09c73ae73d
 labs/buildroot-new-packages/buildroot-new-packages.tex | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/labs/buildroot-new-packages/buildroot-new-packages.tex b/labs/buildroot-new-packages/buildroot-new-packages.tex
index a4209810..19530757 100644
--- a/labs/buildroot-new-packages/buildroot-new-packages.tex
+++ b/labs/buildroot-new-packages/buildroot-new-packages.tex
@@ -203,3 +203,15 @@ Now, to experiment with Buildroot, do the following test: disable the
 doing \code{make}. Once the build is done (which should be very
 quick), looked in \code{output/target/}. Is {\em nInvaders} still
 installed? If so, why?
+
+\section{Sanity checking your package}
+
+If you want to verify if your package matches the coding style rules
+of Buildroot, you can run:
+
+\begin{verbatim}
+make check-package
+\end{verbatim}
+
+While a successful result doesn't mean your package is perfect, it at
+least verifies a number of basic requirements.