people should email licensing@fsf.org, not compliance@fsf.org
This commit is contained in:
parent
9ab67f3125
commit
a577a77eb4
1 changed files with 8 additions and 8 deletions
16
gpl-lgpl.tex
16
gpl-lgpl.tex
|
@ -4077,7 +4077,7 @@ because a deep understanding of how compiler programs work is nearly
|
||||||
mandatory to grasp the subtle nature of what LGPLv2.1~\S5, \P 4 seeks to
|
mandatory to grasp the subtle nature of what LGPLv2.1~\S5, \P 4 seeks to
|
||||||
cover. It helps some to note that this is a border case that we cover in
|
cover. It helps some to note that this is a border case that we cover in
|
||||||
the license only so that when such a border case is hit, the implications
|
the license only so that when such a border case is hit, the implications
|
||||||
of using LGPL continue in the expected way.
|
of using the LGPL continue in the expected way.
|
||||||
|
|
||||||
To understand this subtle point, we must recall the way that a compiler
|
To understand this subtle point, we must recall the way that a compiler
|
||||||
operates. The compiler first generates object code, which are the binary
|
operates. The compiler first generates object code, which are the binary
|
||||||
|
@ -4157,8 +4157,8 @@ If such a mechanism is used, it must allow the user to upgrade and
|
||||||
replace the library with interface-compatible versions and still be able
|
replace the library with interface-compatible versions and still be able
|
||||||
to use the ``work that uses the library.'' However, all modern shared
|
to use the ``work that uses the library.'' However, all modern shared
|
||||||
library mechanisms function as such, and thus LGPLv2.1~\S6(b) is the simplest
|
library mechanisms function as such, and thus LGPLv2.1~\S6(b) is the simplest
|
||||||
option, since it does not even require that the distributor of the ``work
|
option, since it does not even require that the distributor of the ``work
|
||||||
2based on the library'' ship copies of the library itself.
|
based on the library'' ship copies of the library itself.
|
||||||
|
|
||||||
LGPLv2.1~\S6(a) is the option to use when, for some reason, a shared library
|
LGPLv2.1~\S6(a) is the option to use when, for some reason, a shared library
|
||||||
mechanism cannot be used. It requires that the source for the library be
|
mechanism cannot be used. It requires that the source for the library be
|
||||||
|
@ -4186,12 +4186,12 @@ permit us to cover in this course.
|
||||||
|
|
||||||
\section{And the Rest}
|
\section{And the Rest}
|
||||||
|
|
||||||
The remaining variations between LGPL and GPL cover the following
|
The remaining variations between the LGPL and the GPL cover the following
|
||||||
conditions:
|
conditions:
|
||||||
|
|
||||||
\begin{itemize}
|
\begin{itemize}
|
||||||
|
|
||||||
\item Allowing a licensing ``upgrade'' from LGPL to GPL\@ (in LGPLv2.1~\S3)
|
\item Allowing a licensing ``upgrade'' from the LGPL to the GPL\@ (in LGPLv2.1~\S3)
|
||||||
|
|
||||||
\item Binary distribution of the library only, covered in LGPLv2.1~\S4,
|
\item Binary distribution of the library only, covered in LGPLv2.1~\S4,
|
||||||
which is effectively equivalent to LGPLv2.1~\S3
|
which is effectively equivalent to LGPLv2.1~\S3
|
||||||
|
@ -4222,7 +4222,7 @@ As discussed in Sections~\ref{GPLv2s0} and~\ref{GPLv2s5} of this tutorial,
|
||||||
the GPL only governs the activities of copying, modifying and
|
the GPL only governs the activities of copying, modifying and
|
||||||
distributing software programs that are not governed by the license.
|
distributing software programs that are not governed by the license.
|
||||||
Thus, in FSF's view, simply installing the software on a machine and
|
Thus, in FSF's view, simply installing the software on a machine and
|
||||||
using it is not controlled or limited in any way by GPL\@. Using Free
|
using it is not controlled or limited in any way by the GPL\@. Using Free
|
||||||
Software in general requires substantially fewer agreements and less
|
Software in general requires substantially fewer agreements and less
|
||||||
license compliance activity than any known proprietary software.
|
license compliance activity than any known proprietary software.
|
||||||
|
|
||||||
|
@ -4272,7 +4272,7 @@ embedded targets. Eventually, Cygnus was so successful that
|
||||||
it was purchased by Red Hat where it remains a profitable division.
|
it was purchased by Red Hat where it remains a profitable division.
|
||||||
|
|
||||||
However, there are very small companies that compete in
|
However, there are very small companies that compete in
|
||||||
this space. Because the code-base is protect by GPL, it creates and
|
this space. Because the code-base is protect by the GPL, it creates and
|
||||||
demands industry trust. Companies can cooperate on the software and
|
demands industry trust. Companies can cooperate on the software and
|
||||||
improve it for everyone. Meanwhile, companies who rely on GCC for their
|
improve it for everyone. Meanwhile, companies who rely on GCC for their
|
||||||
work are happy to pay for improvements, and for ports to new target
|
work are happy to pay for improvements, and for ports to new target
|
||||||
|
@ -4327,7 +4327,7 @@ making a profit.
|
||||||
|
|
||||||
Note that FSF does provide services to assist companies who need
|
Note that FSF does provide services to assist companies who need
|
||||||
assistance in complying with the GPL. You can contact FSF's GPL
|
assistance in complying with the GPL. You can contact FSF's GPL
|
||||||
Compliance Labs at $<$compliance@fsf.org$>$.
|
Compliance Labs at $<$licensing@fsf.org$>$.
|
||||||
|
|
||||||
%FIXME-LATER: should have \tutorialpart
|
%FIXME-LATER: should have \tutorialpart
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue