Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Link LGPL compliance section to LGPL analysis.

Browse source 
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.)
This commit is contained in:
Bradley M. Kuhn 2014-11-11 19:19:57 -05:00
parent 8b4497c6db
commit 746eff5786
2 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
compliance-guide.tex
View file

@ -1209,15 +1209,15 @@ particular interest.
GPL compliance and LGPL compliance mostly involve the same issues. As we GPL compliance and LGPL compliance mostly involve the same issues. As we
discussed in \S~\ref{derivative-works}, questions of modified versions of 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 overview document. The LGPL adds some additional complexity to the
analysis. Namely, the various LGPL versions permit proprietary licensing analysis. Namely, the various LGPL versions permit proprietary licensing
of certain types of modified versions. These issues are well beyond the of certain types of modified versions. These issues are discussed in greater
scope of this document, but as a rule of thumb, once you have determined 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'' (in accordance with LGPLv3) what part of the work is the ``Application''
and what portions of the source are ``Minimal Corresponding Source'', then and what portions of the source are ``Minimal Corresponding Source'', then
you can usually proceed to follow the GPL compliance rules that we you can usually proceed to follow the GPL compliance rules that
discussed, replacing our discussion of ``Corresponding Source'' with discussed above, replacing our discussion of ``Corresponding Source'' with
``Minimal Corresponding Source''. ``Minimal Corresponding Source''.
LGPL also requires that you provide a mechanism to combine the Application LGPL also requires that you provide a mechanism to combine the Application

2
gpl-lgpl.tex
View file

@ -4113,6 +4113,7 @@ Terms to Your New Programs'' to just the bare essentials.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\chapter{The Lesser GPL} \chapter{The Lesser GPL}
\label{LGPLv2}
As we have seen in our consideration of the GPL, its text is specifically 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 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 % FIXME-URGENT: integrate
\chapter{LGPLv3} \chapter{LGPLv3}
\label{LGPLv3}
LGPLv3 was designed to rectify the architectural plan of the GNU family of 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 licenses, by making the copyleft license from which LGPLv3 is a combination