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

Integrate this short sentence from pasted text.

Browse source 
This was easily integrated, but I am now not sure what I was thinking
with the FIXME note about linking back to the copyleft definition.  The
right link is a forward-link to the derivative works chapter, and thus
I've added that.
This commit is contained in:
Bradley M. Kuhn 2014-11-12 07:50:28 -05:00
parent e36a9a4f4c
commit 5e195ab80a
1 changed files with 6 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
gpl-lgpl.tex
View file

@ -1126,18 +1126,16 @@ fact, has no control over the rules of copyright themselves. Such rules are
the domain of copyright law and the courts --- not the licenses that utilize
those systems.
Copyright law as a whole doesn't propose clear and straightforward guidelines
Copyright law as a whole does not propose clear and straightforward guidelines
for identifying the derivative and/or combined works of software. However,
no copyright license --- not even the GNU GPL --- can be blamed for this.
Legislators and court opinions must give us guidance in borderline cases.
% FIXME-URGENT: integrate (and back ref to copyleft section)
A
lawyer’s conclusion on that subject will be based on the application of rules
Meanwhile, lawyers will likely based their conclusions on the application of rules
made in the context of literary or artistic copyright to the different
context of computer programming.
%FIXME-URGENT: end
context of computer programming and by analyzing the (somewhat limited) case
law and guidance available from various sources.
(Chapter~\ref{derivative-works} discusses this issue in depth.)
\section{GPLv2~\S1: Verbatim Copying}
\label{GPLv2s1}