the gpl
This commit is contained in:
parent
33e47ace60
commit
f58920bbe5
1 changed files with 2 additions and 2 deletions
|
@ -2802,7 +2802,7 @@ in \S~\ref{GPLv2s3} of this tutorial), the distribution of object code may
|
|||
either be accompanied by the machine-readable source code, or it may be
|
||||
accompanied by a valid written offer to provide the machine-readable source
|
||||
code. However, unlike in GPLv2, that offer cannot be exercised by any third
|
||||
party; rather, only those ``who possesses the object code'' it can exercised
|
||||
party; rather, only those ``who possesses the object code'' can exercise
|
||||
the offer. (Note that this is a substantial narrowing of requirements of
|
||||
offer fulfillment, and is a wonderful counterexample to dispute claims that
|
||||
the GPLv3 has more requirements than GPLv2.)
|
||||
|
@ -2947,7 +2947,7 @@ GPLv3 drafting process. However, companies and governments that use
|
|||
specialized or enterprise-level computer facilities reported that they
|
||||
actually \textit{want} their systems not to be under their own control.
|
||||
Rather than agreeing to this as a concession, or bowing to pressure, they ask
|
||||
for this as a \textit{preference}. It is not clear that GPL should interfere
|
||||
for this as a \textit{preference}. It is not clear that the GPL should interfere
|
||||
here, since the main problem lies elsewhere.
|
||||
|
||||
While imposing technical barriers to modification is wrong regardless of
|
||||
|
|
Loading…
Reference in a new issue