[FE training-materials-updates] LGPL: stop saying that dynamic linking must be used

[Michael Opdenacker]

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

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

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

commit 28616abb323cb2e64977a889559de798d4a18f9a
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Fri Mar 28 05:33:03 2014 +0100

    LGPL: stop saying that dynamic linking must be used
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

28616abb323cb2e64977a889559de798d4a18f9a
 .../sysdev-embedded-linux.tex                      |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index 55aff44..5f1a999 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -197,10 +197,12 @@
     \begin{itemize}
     \item Modified versions must be released under the same license
     \item But, programs linked against a library under the LGPL do not
-      need to be released under the LGPL and can be kept proprietary
+      need to be released under the LGPL and can be kept proprietary.
     \item However, the user must keep the ability to update the
-      library independently from the program, so dynamic linking must
-      be used
+      library independently from the program. Dynamic linking is the
+      easiest solution. Statically linked executables are only possible
+      if the developer provides a way to relink with an update
+      (with source code or linkable object files).
     \end{itemize}
   \item Used instead of the GPL for most of the libraries, including
     the C libraries