From 746eff5786b239d829dc982565f5e7f0a9c6edf4 2014-11-12 00:21:21 From: Bradley M. Kuhn Date: 2014-11-12 00:21:21 Subject: [PATCH] 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.) --- diff --git a/compliance-guide.tex b/compliance-guide.tex index 256e5dd7e92fc1ffd7f32ff53aad2d8f86bdf735..4f6a580113f022d115249706fc9fee45c8418b15 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -1209,15 +1209,15 @@ particular interest. 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 diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex index af821593ffef0a5c36daaa2c1a42e305c3a78d28..ca6afc096fb6554852638f3803e44b5e16766be6 100644 --- a/gpl-lgpl.tex +++ b/gpl-lgpl.tex @@ -4113,6 +4113,7 @@ 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 @@ -4683,6 +4684,7 @@ 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