Changeset - 7a755cf4cbab
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-03-20 14:11:47
bkuhn@ebb.org
Correct various references and labels to consistency.
1 file changed with 9 insertions and 6 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -962,7 +962,7 @@ version of the GPL published by the FSF).  However, the FSF \textbf{does not
 
its authority for future licensing decisions to the FSF.  In fact, the FSF
 
considered this possibility for GPLv3 and chose not to do so, instead opting
 
for the third-party steward designation clause discussed in
 
Section~\ref{GPlv3S14}.
 
Section~\ref{GPLv3s14}.
 

	
 
\section{Complexities of Two Simultaneously Popular Copylefts}
 

	
...
 
@@ -1459,6 +1459,7 @@ software. These sections, GPLv2~\S\S2--3, define the central core rights and
 
requirements of GPLv2\@.
 

	
 
\section{GPLv2~\S2: Share and Share Alike}
 
\label{GPLv2s2}
 

	
 
For many, this is where the ``magic'' happens that defends software
 
freedom upon redistribution.  GPLv2~\S2 is the only place in GPLv2
...
 
@@ -1624,7 +1625,7 @@ as long as the terms of GPL are adhered to for those packages that are
 
truly GPL'd.
 

	
 
\section{GPLv2~\S3: Producing Binaries}
 
\label{GPL-Section-3}
 
\label{GPLv2s3}
 

	
 
Software is a strange beast when compared to other copyrightable works.
 
It is currently impossible to make a film or a book that can be truly
...
 
@@ -1748,7 +1749,7 @@ As is shown above, Under GPLv2~\S3(a), embedded manufacturers can put the
 
binaries on the device and ship the source code along on a CD\@.  However,
 
sometimes this turns out to be too costly.  Including a CD with every
 
device could prove too costly, and may practically (although not legally)
 
prohibit using GPL'd software. For this situation and others like it, GPlv2\S~3(b) is available.
 
prohibit using GPL'd software. For this situation and others like it, GPLv2\S~3(b) is available.
 

	
 
GPLv2~\S3(b) allows a distributor of binaries to instead provide a written
 
offer for source code alongside those binaries.  This is useful in two
...
 
@@ -2526,7 +2527,7 @@ is that the library in question does not qualify for it.
 
\section{GPLv3~\S2: Basic Permissions}
 

	
 
GPLv3~\S2 can roughly be considered as an equivalent to GPLv2~\S0 (discussed
 
in \S~\ref{GPLv2sS0} of this tutorial).  However, the usual style of
 
in \S~\ref{GPLv2s0} of this tutorial).  However, the usual style of
 
improvements found in GPLv3 are found here as well.  For example, the first
 
sentence of GPLv3~\S2 furthers the goal internationalization.  Under the
 
copyright laws of some countries, it may be necessary for a copyright license
...
 
@@ -2731,6 +2732,7 @@ those who convey GPL-covered software may offer commercial services for the
 
support of that software.
 

	
 
\section{GPLv3~\S5: Modified Source}
 
\label{GPLv3s5}
 

	
 
% FIXME: 5(a) is slightly different in final version
 

	
...
 
@@ -2783,6 +2785,7 @@ they and the old program form must be licensed under the GPL.  As subsection
 
5c states, packaging of a work has no bearing on the scope of copyleft.
 

	
 
\section{GPLv3~\S6: Non-Source and Corresponding Source}
 
\label{GPLv3s6}
 

	
 
Section 6 of GPLv3, which clarifies and revises GPLv2 section 3, requires
 
distributors of GPL'd object code to provide access to the corresponding
...
 
@@ -4296,7 +4299,7 @@ GPL should recognize that most other free software licenses also permit
 
such linking. 
 

	
 
\section{GPLv3~\S14: So, When's GPLv4?}
 
\label{GPlv2s14}
 
\label{GPLv3s14}
 

	
 
% FIXME Say more
 

	
...
 
@@ -4555,7 +4558,7 @@ works and source code derivatives. We will first consider the definition
 
of a ``work that uses the library,'' which is set forth in LGPLv2.1~\S5.
 

	
 
We noted in our discussion of GPLv2~\S3 (discussed in
 
Section~\ref{GPL-Section-3} of this document) that binary programs when
 
Section~\ref{GPLv2s3} of this document) that binary programs when
 
compiled and linked with GPL'd software are derivative works of that GPL'd
 
software. This includes both linking that happens at compile-time (when
 
the binary is created) or at runtime (when the binary -- including library
0 comments (0 inline, 0 general)