Copyleft/guide Changeset - 9ab67f312539

Changeset - 9ab67f312539

Parent rev.

Child rev.

[Not reviewed]

0 1 0

donaldr3 - 10 years ago 2014-03-21 23:23:04
donald@copyrighteous.office.fsf.org

the

1 file changed with 5 insertions and 5 deletions:

gpl-lgpl.tex

0 comments (0 inline, 0 general)

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 the library,'' and ``works based on the library.''  Unlike the GPL, the LGPL must
 draw some lines regarding derivative works. We do this here in this
 license because we specifically seek to liberalize the rights afforded to
 those who make derivative works. In GPL, we reach as far as copyright law
 allows. In LGPL, we want to draw a line that allows some derivative works
 those who make derivative works. In the GPL, we reach as far as copyright law
 allows. In the LGPL, we want to draw a line that allows some derivative works
 copyright law would otherwise prohibit if the copyright holder exercised
 his full permitted controls over the work.
 \section{An Application: A Work that Uses the Library}
 In the effort to allow certain proprietary derivative works and prohibit
 others, LGPL distinguishes between two classes of derivative works:
+others, the LGPL distinguishes between two classes of derivative works:
 ``works based on the library,'' and ``works that use the library.''  The
 distinction is drawn on the bright line of binary (or runtime) derivative
 works and source code derivatives. We will first consider the definition
@@ ... / @@ -3976,7 +3976,7 @@ the library,'' works as follows: @@
 \item Since \lplusi{} is a derivative work of both \worki{} and \workl{},
   the license of \workl{} (the LGPL) can put restrictions on the license
   of \lplusi{}. In fact, this is what LGPL does.
+  of \lplusi{}. In fact, this is what the LGPL does.
 \end{itemize}
@@ ... @@
 derivative work of LGPL'd software that cannot otherwise fit the
 definition of a ``work that uses the library.''  A ``work based on the
 library'' extends the full width and depth of copyright derivative works,
 in the same sense that GPL does.
+in the same sense that the GPL does.
 Most typically, one creates a ``work based on the library'' by directly
 modifying the source of the library. Such a work could also be created by

0 comments (0 inline, 0 general)