GPLv3 clarifies private modification permission.
While both GPLv2 and GPLv3 have long been considered to grant unabridged right to private modification, GPLv3 has much clearer and explicit wording to this effect. This should be noted when that paragraph is explained. This change herein does that. HT Wolvereness for pointing this difference between GPLv2 and GPLv3 out to me.
This commit is contained in:
parent
558297c9c1
commit
e5ee0fd0a1
1 changed files with 4 additions and 1 deletions
|
@ -2556,7 +2556,10 @@ unfortunate restrictions on the freedom to run.\footnote{See
|
||||||
GPLv3~\S2\P2 distinguishes between activities of a licensee that are
|
GPLv3~\S2\P2 distinguishes between activities of a licensee that are
|
||||||
permitted without limitation and activities that trigger additional
|
permitted without limitation and activities that trigger additional
|
||||||
requirements. Specifically, GPLv3~\S2\P2 guarantees the basic freedoms of
|
requirements. Specifically, GPLv3~\S2\P2 guarantees the basic freedoms of
|
||||||
privately modifying and running the program.
|
privately modifying and running the program. While these basic freedoms were
|
||||||
|
generally considered a standard part of users' rights under GPLv2 as well,
|
||||||
|
the GPLv3 states them herein more explicitly. (In other words, there is no
|
||||||
|
direct analog to the first sentence of GPLv3~\S2\P2 in GPLv2.)
|
||||||
|
|
||||||
Also, GPLv3~\S2\P2 gives an explicit permission for a client to provide a
|
Also, GPLv3~\S2\P2 gives an explicit permission for a client to provide a
|
||||||
copy of its modified software to a contractor exclusively for that contractor
|
copy of its modified software to a contractor exclusively for that contractor
|
||||||
|
|
Loading…
Reference in a new issue