Changeset - 387f2c4ace6e
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-11-12 18:59:04
bkuhn@ebb.org
Incorporate pasted text into intro paragraph.

Some of this text was useful as part of the introduction paragraph.
1 file changed with 10 insertions and 13 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -3046,27 +3046,24 @@ paragraph of GPLv3\S5, which now also covers issues related to copyright
 
compilations (but not compilations into object code --- that's in the next
 
section!).  The intent and scope is the same as was intended in GPLv2.
 

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

	
 
%FIXME-URGENT: integrate
 

	
 
Section 6 states the compliance obligations for distributing ``non-source
 
forms'' of a program, which means any form other than the form preferred for
 
making modifications. In addition to binaries or executables, non-source
 
GPLv3~\S6 states the compliance obligations for distributing ``non-source
 
forms'' of a program (which means any form other than CCS).  As noted in \S~\ref{GPLv3s0}, ``object code'' in GPLv3
 
is defined broadly to mean any non-source version of a work, and thus
 
includes not only binaries or executables, non-source
 
forms therefore include obfuscated, minimized, compressed or otherwise
 
non-preferred forms for modification. The requirement to provide complete and corresponding source code under \S6
 
closely parallels the provisions of GPLv2 \S3, above, but with changes
 
non-preferred forms for modification.  Thus, GPLv3~\S6 clarifies and revises GPLv2~\S3.
 
Indeed, GPLv3~\S6's CCS requirement under
 
closely parallels the provisions of \hyperref[GPLv2s3]{GPLv2~\S3}, with changes
 
designed to make compliant provisioning easier under contemporary
 
technological conditions.
 
% FIXME-URGENT: end
 
GPLv3~\S6 clarifies and revises GPLv2~\S3.  It requires distributors of GPL'd
 
object code to provide access to the corresponding source code, in one of
 
four specified ways.  As noted in \S~\ref{GPLv3s0}, ``object code'' in GPLv3
 
is defined broadly to mean any non-source version of a work.
 
technological conditions.  Distributors of GPLv3'd
 
object code must provide access to the corresponding source code, in one of
 
four specified ways.
 

	
 
% FIXME:  probably mostly still right, needs some updates, though.
 

	
 
GPLv3~\S6(a--b) now apply specifically to distribution of object code in a
 
physical product.  Physical products include embedded systems, as well as
 
physical software distribution media such as CDs.  As in GPLv2~\S3 (discussed
0 comments (0 inline, 0 general)