Changeset - 37f3a75b9db7
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-03-19 13:50:51
bkuhn@ebb.org
Merge these two paragraphs into one.
1 file changed with 9 insertions and 12 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -2259,2 +2259,4 @@ source or obfuscated programming.
 

	
 
% FIXME: CCS Coresponding Source updated to newer definition in later drafts
 

	
 
Keeping with the desire to ``round up'' definitions that were spread
...
 
@@ -2270,14 +2272,9 @@ throughout the text of GPLv2, the definition of CCS\footnote{Note that the
 
  term of ``Corresponding Source''.}, or, as GPLv3 officially calls it,
 
``Corresponding Source'', is given in GPLv3~\S1\P4
 

	
 
% FIXME: CCS Coresponding Source updated to newer definition in later drafts
 

	
 
This definition of ``Corresponding Source''
 
is as broad as necessary to protect users'
 
exercise of their rights under the GPL. We follow the definition with
 
particular examples to remove any doubt that they are to be considered
 
Complete Corresponding Source Code. We wish to make completely clear
 
that a licensee cannot avoid complying with the requirements of the GPL
 
by dynamically linking an add-on component to the original version of a
 
program.
 
``Corresponding Source'', is given in GPLv3~\S1\P4.  This definition is as
 
broad as necessary to protect users' exercise of their rights under the
 
GPL. We follow the definition with particular examples to remove any doubt
 
that they are to be considered Complete Corresponding Source Code. We wish to
 
make completely clear that a licensee cannot avoid complying with the
 
requirements of the GPL by dynamically linking an add-on component to the
 
original version of a program.
 

	
0 comments (0 inline, 0 general)