Copyleft/guide Changeset - 746eff5786b2

Changeset - 746eff5786b2

Parent rev.

Child rev.

[Not reviewed]

0 2 0

Bradley Kuhn (bkuhn) - 9 years ago 2014-11-12 00:21:21
bkuhn@ebb.org

Link LGPL compliance section to LGPL analysis.

Since so little material is currently given on LGPL compliance, it's
likely best to link back to the chapter on LGPL compliance.

Besides, I don't think there really is anything additional the
compliance guide can add regarding LGPL compliance, other than the
detail license analysis on LGPL already available in that part of the
text.

(Note labels had to be added for the chapters that didn't previously
exist.)

2 files changed with 7 insertions and 5 deletions:

compliance-guide.tex

gpl-lgpl.tex

0 comments (0 inline, 0 general)

compliance-guide.tex

➞

Show inline comments

@@ ... / @@ -1206,21 +1206,21 @@ particular interest. @@
 \section{LGPL Compliance}
 \label{lgpl}
 GPL compliance and LGPL compliance mostly involve the same issues.  As we
 discussed in \S~\ref{derivative-works}, questions of modified versions of
-software are highly fact-dependant and cannot be easily addressed in any
+software are highly fact-dependent and cannot be easily addressed in any
 overview document.  The LGPL adds some additional complexity to the
 analysis.  Namely, the various LGPL versions permit proprietary licensing
 of certain types of modified versions.  These issues are well beyond the
 scope of this document, but as a rule of thumb, once you have determined
 of certain types of modified versions.  These issues are discussed in greater
 detail in Chapter~\ref{LGPLv2} and~\ref{LGPLv3}.  However, as a rule of thumb, once you have determined
 (in accordance with LGPLv3) what part of the work is the ``Application''
 and what portions of the source are ``Minimal Corresponding Source'', then
 you can usually proceed to follow the GPL compliance rules that we
 discussed, replacing our discussion of ``Corresponding Source'' with
 you can usually proceed to follow the GPL compliance rules that
 discussed above, replacing our discussion of ``Corresponding Source'' with
 ``Minimal Corresponding Source''.
 LGPL also requires that you provide a mechanism to combine the Application
 with a modified version of the library, and outlines some options for
 this.  Also, the license of the whole work must permit ``reverse
 engineering for debugging such modifications'' to the library.  Therefore,

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 Finally, the FSF shortened the section on ``How to Apply These
 Terms to Your New Programs'' to just the bare essentials.
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \chapter{The Lesser GPL}
 \label{LGPLv2}
 As we have seen in our consideration of the GPL, its text is specifically
 designed to cover all possible derivative, modified and/or combined works under copyright law. Our
 goal in designing the GPL was to maximize its use of the controls of
 copyright law to maximize the number of works that were covered by GPL.
@@ ... @@
 remainder of LGPLv2.1 is close enough to GPL that the concepts discussed in
 our more extensive GPL unit can be directly applied.
 % FIXME-URGENT: integrate
 \chapter{LGPLv3}
 \label{LGPLv3}
 LGPLv3 was designed to rectify the architectural plan of the GNU family of
 licenses, by making the copyleft license from which LGPLv3 is a combination
 exception GPLv3. LGPLv3 is therefore an additional permission in the form
 provided for in GPLv3 \S7, above.

0 comments (0 inline, 0 general)