[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses gpl-faq.html old-licenses/gpl-2.0-...
|
From: |
Pavel Kharitonov |
|
Subject: |
www/licenses gpl-faq.html old-licenses/gpl-2.0-... |
|
Date: |
Sat, 11 Mar 2017 02:41:36 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: Pavel Kharitonov <ineiev> 17/03/11 02:41:36
Modified files:
licenses : gpl-faq.html
licenses/old-licenses: gpl-2.0-faq.html
Log message:
s/non-free/nonfree/
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.html?cvsroot=www&r1=1.230&r2=1.231
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-faq.html?cvsroot=www&r1=1.37&r2=1.38
Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.230
retrieving revision 1.231
diff -u -b -r1.230 -r1.231
--- gpl-faq.html 10 Mar 2017 21:22:38 -0000 1.230
+++ gpl-faq.html 11 Mar 2017 07:41:36 -0000 1.231
@@ -101,7 +101,7 @@
public?</a></li>
<li><a href="#GPLAndNonfreeOnSameMachine">Can I have a GPL-covered
- program and an unrelated non-free program on the same computer?</a></li>
+ program and an unrelated nonfree program on the same computer?</a></li>
<li><a href="#CanIDemandACopy">If I know someone has a copy of a
GPL-covered program, can I demand they give me a copy?</a></li>
@@ -304,7 +304,7 @@
<li><a href="#ReleaseUnderGPLAndNF">I would like to release a
program I wrote under the GNU GPL, but I would like to use the same
- code in non-free programs.</a></li>
+ code in nonfree programs.</a></li>
<li><a href="#CanDeveloperThirdParty">Can the developer of a program
who distributed it under the GPL later license it to another party
@@ -339,7 +339,7 @@
system templates?</a></li>
<li><a href="#NonFreeTools">Can I release a program under the GPL
- which I developed using non-free tools?</a></li>
+ which I developed using nonfree tools?</a></li>
<li><a href="#GiveUpKeys">I use public key cryptography to sign my
code to assure its authenticity. Is it true that GPLv3 forces me to
@@ -488,11 +488,11 @@
<ul>
<li><a href="#GPLAndNonfreeOnSameMachine">Can I have a GPL-covered
- program and an unrelated non-free program on the same
+ program and an unrelated nonfree program on the same
computer?</a></li>
<li><a href="#CanIUseGPLToolsForNF">Can I use GPL-covered editors
- such as GNU Emacs to develop non-free programs? Can I use
+ such as GNU Emacs to develop nonfree programs? Can I use
GPL-covered tools such as GCC to compile them?</a></li>
<li><a href="#GPLOutput">Is there some way that I can GPL the output
@@ -595,9 +595,9 @@
on the licenses I can use for distributing my plug-in?</a></li>
<li><a href="#GPLPluginsInNF">Can I apply the GPL when writing a
- plug-in for a non-free program?</a></li>
+ plug-in for a nonfree program?</a></li>
- <li><a href="#NFUseGPLPlugins">Can I release a non-free program
+ <li><a href="#NFUseGPLPlugins">Can I release a nonfree program
that's designed to load a GPL-covered plug-in?</a></li>
<li><a href="#GPLInProprietarySystem">I'd like to incorporate
@@ -612,7 +612,7 @@
and the proprietary part?</a></li>
<li><a href="#FSWithNFLibs">Can I write free software that uses
- non-free libraries?</a></li>
+ nonfree libraries?</a></li>
<li><a href="#SystemLibraryException">Can I link a GPL program with
a proprietary system library?</a></li>
@@ -833,7 +833,7 @@
<dt id="GPLAndNonfreeOnSameMachine">Can I have a GPL-covered
- program and an unrelated non-free program on the same computer?
+ program and an unrelated nonfree program on the same computer?
<span class="anchor-reference-id">(<a href="#GPLAndNonfreeOnSameMachine"
>#GPLAndNonfreeOnSameMachine</a>)</span></dt>
<dd><p>Yes.</p></dd>
@@ -952,7 +952,7 @@
<span class="anchor-reference-id">(<a href="#DoesTheGPLAllowRequireFee"
>#DoesTheGPLAllowRequireFee</a>)</span></dt>
<dd><p>
-No. In fact, a requirement like that would make the program non-free.
+No. In fact, a requirement like that would make the program nonfree.
If people have to pay when they get a copy of a program, or if they
have to notify anyone in particular, then the program is not free.
See the <a href="/philosophy/free-sw.html">
@@ -1202,29 +1202,29 @@
<dt id="FSWithNFLibs">Can I write
- free software that uses non-free libraries?
+ free software that uses nonfree libraries?
<span class="anchor-reference-id">(<a href="#FSWithNFLibs"
>#FSWithNFLibs</a>)</span></dt>
<dd><p>
If you do this, your program won't be fully usable in a free
-environment. If your program depends on a non-free library to do a
+environment. If your program depends on a nonfree library to do a
certain job, it cannot do that job in the Free World. If it depends on a
-non-free library to run at all, it cannot be part of a free operating
+nonfree library to run at all, it cannot be part of a free operating
system such as GNU; it is entirely off limits to the Free World.</p>
<p>So please consider: can you find a way to get the job done without using
this library? Can you write a free replacement for that library?</p>
-<p>If the program is already written using the non-free library, perhaps it
+<p>If the program is already written using the nonfree library, perhaps it
is too late to change the decision. You may as well release the program
as it stands, rather than not release it. But please mention in the
-README that the need for the non-free library is a drawback, and suggest
+README that the need for the nonfree library is a drawback, and suggest
the task of changing the program so that it does the same job without
-the non-free library. Please suggest that anyone who thinks of doing
+the nonfree library. Please suggest that anyone who thinks of doing
substantial further work on the program first free it from dependence
-on the non-free library.</p>
+on the nonfree library.</p>
-<p>Note that there may also be legal issues with combining certain non-free
+<p>Note that there may also be legal issues with combining certain nonfree
libraries with GPL-covered free software. Please see <a
href="#GPLIncompatibleLibs">the question on GPL software with
GPL-incompatible libraries</a> for more information.</p></dd>
@@ -1270,9 +1270,9 @@
<p>When other people modify the program, they do not have to make the same
exception for their code—it is their choice whether to do so.</p>
-<p>If the libraries you intend to link with are non-free, please also see
+<p>If the libraries you intend to link with are nonfree, please also see
<a href="#FSWithNFLibs">the section on writing Free Software which uses
-non-free libraries</a>.</p>
+nonfree libraries</a>.</p>
<p>If you're using GPLv3, you can accomplish this goal by granting an
additional permission under section 7. The following license notice will
@@ -1438,11 +1438,11 @@
<dt id="ReleaseUnderGPLAndNF">I would like to release a program I wrote
under the GNU GPL, but I would
- like to use the same code in non-free programs.
+ like to use the same code in nonfree programs.
<span class="anchor-reference-id">(<a href="#ReleaseUnderGPLAndNF"
>#ReleaseUnderGPLAndNF</a>)</span></dt>
<dd><p>
-To release a non-free program is always ethically tainted, but
+To release a nonfree program is always ethically tainted, but
legally there is no obstacle to your doing this. If you are the copyright
holder for the code, you can release it under various different
non-exclusive licenses at various times.</p></dd>
@@ -1474,7 +1474,7 @@
<dt id="CanIUseGPLToolsForNF">Can I use GPL-covered editors such as
- GNU Emacs to develop non-free programs? Can I use GPL-covered tools
+ GNU Emacs to develop nonfree programs? Can I use GPL-covered tools
such as GCC to compile them?
<span class="anchor-reference-id">(<a href="#CanIUseGPLToolsForNF"
>#CanIUseGPLToolsForNF</a>)</span></dt>
@@ -1490,11 +1490,11 @@
part of the output which is derived from the program's input inherits
the copyright status of the input.</p>
-<p>As it happens, Bison can also be used to develop non-free programs.
+<p>As it happens, Bison can also be used to develop nonfree programs.
This is because we decided to explicitly permit the use of the Bison
standard parser program in Bison output files without restriction. We
made the decision because there were other tools comparable to Bison
-which already permitted use for non-free programs.</p></dd>
+which already permitted use for nonfree programs.</p></dd>
<dt id="GPLFairUse">Do I have “fair use”
@@ -1797,7 +1797,7 @@
<dt id="GPLPluginsInNF">Can I apply the
- GPL when writing a plug-in for a non-free program?
+ GPL when writing a plug-in for a nonfree program?
<span class="anchor-reference-id">(<a href="#GPLPluginsInNF"
>#GPLPluginsInNF</a>)</span></dt>
<dd><p>
@@ -1806,16 +1806,16 @@
and when they are considered separate programs</a>.</p>
<p> If they form a
single combined program this means that combination of the GPL-covered
-plug-in with the non-free main program would violate the GPL. However,
+plug-in with the nonfree main program would violate the GPL. However,
you can resolve that legal problem by adding an exception to your
-plug-in's license, giving permission to link it with the non-free main
+plug-in's license, giving permission to link it with the nonfree main
program.</p>
<p>See also the question <a href="#FSWithNFLibs">I am
-writing free software that uses a non-free library.</a></p></dd>
+writing free software that uses a nonfree library.</a></p></dd>
-<dt id="NFUseGPLPlugins">Can I release a non-free program
+<dt id="NFUseGPLPlugins">Can I release a nonfree program
that's designed to load a GPL-covered plug-in?
<span class="anchor-reference-id">(<a href="#NFUseGPLPlugins"
>#NFUseGPLPlugins</a>)</span></dt>
@@ -1834,7 +1834,7 @@
makes no requirements about the main program.</p>
<p>See also the question <a href="#FSWithNFLibs">I am
-writing free software that uses a non-free library.</a></p></dd>
+writing free software that uses a nonfree library.</a></p></dd>
<dt id="LinkingWithGPL">You have a GPL'ed program that I'd like
@@ -1958,7 +1958,7 @@
An “aggregate” consists of a number of separate programs,
distributed together on the same CD-ROM or other media. The GPL permits
you to create and distribute an aggregate, even when the licenses of the
-other software are non-free or GPL-incompatible. The only condition is
+other software are nonfree or GPL-incompatible. The only condition is
that you cannot release the aggregate under a license that prohibits users
from exercising rights that each program's individual license would
grant them.</p>
@@ -2110,8 +2110,8 @@
You cannot incorporate GPL-covered software in a proprietary system.
The goal of the GPL is to grant everyone the freedom to copy,
redistribute, understand, and modify a program. If you could
-incorporate GPL-covered software into a non-free system, it would have
-the effect of making the GPL-covered software non-free too.</p>
+incorporate GPL-covered software into a nonfree system, it would have
+the effect of making the GPL-covered software nonfree too.</p>
<p>A system incorporating a GPL-covered program is an extended version of
that program. The GPL says that any extended version of the program
@@ -2122,7 +2122,7 @@
<p>However, in many cases you can distribute the GPL-covered software
alongside your proprietary system. To do this validly, you must make
-sure that the free and non-free programs communicate at arms length,
+sure that the free and nonfree programs communicate at arms length,
that they are not combined in a way that would make them
effectively a single program.</p>
@@ -2674,7 +2674,7 @@
<dt id="NonFreeTools">Can I release
- a program under the GPL which I developed using non-free tools?
+ a program under the GPL which I developed using nonfree tools?
<span class="anchor-reference-id">(<a href="#NonFreeTools"
>#NonFreeTools</a>)</span></dt>
<dd><p>
@@ -2682,7 +2682,7 @@
study it, or record it, usually makes no difference for issues
concerning the licensing of that source code.</p>
-<p>However, if you link non-free libraries with the source code, that
+<p>However, if you link nonfree libraries with the source code, that
would be an issue you need to deal with. It does not preclude
releasing the source code under the GPL, but if the libraries don't
fit under the “system library” exception, you should affix
@@ -2837,7 +2837,7 @@
their licenses are. Most system libraries either use the <a
href="/licenses/lgpl.html">GNU Lesser GPL</a>, or use the GNU GPL plus an
exception permitting linking the library with anything. These libraries
-can be used in non-free programs; but in the case of the Lesser GPL, it
+can be used in nonfree programs; but in the case of the Lesser GPL, it
does have some requirements you must follow.</p>
<p>Some libraries are released under the GNU GPL alone; you must use a
@@ -3896,7 +3896,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/10 21:22:38 $
+$Date: 2017/03/11 07:41:36 $
<!-- timestamp end -->
</p>
</div>
Index: old-licenses/gpl-2.0-faq.html
===================================================================
RCS file: /web/www/www/licenses/old-licenses/gpl-2.0-faq.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -b -r1.37 -r1.38
--- old-licenses/gpl-2.0-faq.html 10 Mar 2017 21:22:40 -0000 1.37
+++ old-licenses/gpl-2.0-faq.html 11 Mar 2017 07:41:36 -0000 1.38
@@ -77,7 +77,7 @@
<li><a href="#GPLAndNonfreeOnSameMachine"
name="TOCGPLAndNonfreeOnSameMachine"> Can I have a GPL-covered
- program and an unrelated non-free program on the same
+ program and an unrelated nonfree program on the same
computer?</a></li>
<li><a href="#CanIDemandACopy" name="TOCCanIDemandACopy">If I know
@@ -188,7 +188,7 @@
<li><a href="#ReleaseUnderGPLAndNF" name="TOCReleaseUnderGPLAndNF">I
would like to release a program I wrote under the GNU GPL, but I would
- like to use the same code in non-free programs.</a></li>
+ like to use the same code in nonfree programs.</a></li>
<li><a href="#CanDeveloperThirdParty"
name="TOCCanDeveloperThirdParty">Can the developer of a program who
@@ -209,7 +209,7 @@
website maintenance system templates?</a></li>
<li><a href="#NonFreeTools" name="TOCNonFreeTools">Can I release
- a program under the GPL which I developed using non-free tools?</a></li>
+ a program under the GPL which I developed using nonfree tools?</a></li>
</ul>
<h4>Distribution of programs released under the GPL</h4>
@@ -298,7 +298,7 @@
<ul>
<li><a href="#CanIUseGPLToolsForNF" name="TOCCanIUseGPLToolsForNF">Can
- I use GPL-covered editors such as GNU Emacs to develop non-free
+ I use GPL-covered editors such as GNU Emacs to develop nonfree
programs? Can I use GPL-covered tools such as GCC to compile
them?</a></li>
@@ -374,10 +374,10 @@
the licenses of a plug-in?</a></li>
<li><a href="#GPLPluginsInNF" name="TOCGPLPluginsInNF">Can I apply the
- GPL when writing a plug-in for a non-free program?</a></li>
+ GPL when writing a plug-in for a nonfree program?</a></li>
<li><a href="#NFUseGPLPlugins" name="TOCNFUseGPLPlugins">Can I
- release a non-free program that's designed to load a GPL-covered
+ release a nonfree program that's designed to load a GPL-covered
plug-in?</a></li>
<li><a href="#GPLInProprietarySystem"
@@ -391,7 +391,7 @@
between the GPL-covered part and the proprietary part?</a></li>
<li><a href="#FSWithNFLibs" name="TOCFSWithNFLibs"> Can I write
- free software that uses non-free libraries?</a></li>
+ free software that uses nonfree libraries?</a></li>
<li><a href="#GPLIncompatibleLibs" name="TOCGPLIncompatibleLibs">
What legal issues come up if I use GPL-incompatible libraries with
@@ -587,7 +587,7 @@
</p></dd>
<dt><b><a href="#TOCGPLAndNonfreeOnSameMachine"
name="GPLAndNonfreeOnSameMachine">
- Can I have a GPL-covered program and an unrelated non-free program on
the same computer?</a></b></dt>
+ Can I have a GPL-covered program and an unrelated nonfree program on
the same computer?</a></b></dt>
<dd>
Yes. The “mere aggregation” clause in the GPL makes this
permission explicit, but that only reinforces what we believe would be
@@ -699,7 +699,7 @@
must pay me a fee and/or notify me?</a></b></dt>
<dd>
-No. In fact, a requirement like that would make the program non-free.
+No. In fact, a requirement like that would make the program nonfree.
If people have to pay when they get a copy of a program, or if they
have to notify anyone in particular, then the program is not free.
See the <a href="/philosophy/free-sw.html">
@@ -868,28 +868,28 @@
<dt><b><a href="#TOCFSWithNFLibs" name="FSWithNFLibs">Can I write
-free software that uses non-free libraries?</a></b></dt>
+free software that uses nonfree libraries?</a></b></dt>
<dd>
If you do this, your program won't be fully usable in a free
-environment. If your program depends on a non-free library to do a
+environment. If your program depends on a nonfree library to do a
certain job, it cannot do that job in the Free World. If it depends on a
-non-free library to run at all, it cannot be part of a free operating
+nonfree library to run at all, it cannot be part of a free operating
system such as GNU; it is entirely off limits to the Free World.
<p>
So please consider: can you find a way to get the job done without using
this library? Can you write a free replacement for that library?</p>
<p>
-If the program is already written using the non-free library, perhaps it
+If the program is already written using the nonfree library, perhaps it
is too late to change the decision. You may as well release the program
as it stands, rather than not release it. But please mention in the
-README that the need for the non-free library is a drawback, and suggest
+README that the need for the nonfree library is a drawback, and suggest
the task of changing the program so that it does the same job without
-the non-free library. Please suggest that anyone who thinks of doing
+the nonfree library. Please suggest that anyone who thinks of doing
substantial further work on the program first free it from dependence
-on the non-free library.</p>
+on the nonfree library.</p>
<p>
-Note that there may also be legal issues with combining certain non-free
+Note that there may also be legal issues with combining certain nonfree
libraries with GPL-covered Free Software. Please see <a
href="#GPLIncompatibleLibs">the question on GPL software with
GPL-incompatible libraries</a> for more information.
@@ -977,9 +977,9 @@
When other people modify the program, they do not have to make the same
exception for their code—it is their choice whether to do so.
</p><p>
-If the libraries you intend to link with are non-free, please also see
+If the libraries you intend to link with are nonfree, please also see
<a href="#FSWithNFLibs">the section on writing Free Software which
-uses non-free libraries</a>.
+uses nonfree libraries</a>.
</p></dd>
<dt><b><a href="#TOCHowIGetCopyright" name="HowIGetCopyright">How do I
@@ -1061,10 +1061,10 @@
<dt><b><a href="#TOCReleaseUnderGPLAndNF" name="ReleaseUnderGPLAndNF">I
would like to release a program I wrote under the GNU GPL, but I would
- like to use the same code in non-free programs.</a></b></dt>
+ like to use the same code in nonfree programs.</a></b></dt>
<dd>
-To release a non-free program is always ethically tainted, but legally
+To release a nonfree program is always ethically tainted, but legally
there is no obstacle to your doing this. If you are the copyright
holder for the code, you can release it under various different
non-exclusive licenses at various times.
@@ -1097,7 +1097,7 @@
<dt><b><a href="#TOCCanIUseGPLToolsForNF"
name="CanIUseGPLToolsForNF">Can I use GPL-covered editors such as
- GNU Emacs to develop non-free programs? Can I use GPL-covered tools
+ GNU Emacs to develop nonfree programs? Can I use GPL-covered tools
such as GCC to compile them?</a></b></dt>
<dd>
@@ -1112,11 +1112,11 @@
Meanwhile, the part of the output which is derived from the program's
input inherits the copyright status of the input.</p>
<p>
-As it happens, Bison can also be used to develop non-free programs.
+As it happens, Bison can also be used to develop nonfree programs.
This is because we decided to explicitly permit the use of the Bison
standard parser program in Bison output files without restriction. We
made the decision because there were other tools comparable to Bison
-which already permitted use for non-free programs.
+which already permitted use for nonfree programs.
</p></dd>
<dt><b><a href="#TOCGPLFairUse" name="GPLFairUse">Do I have
@@ -1346,7 +1346,7 @@
<dt><b><a href="#TOCGPLPluginsInNF" name="GPLPluginsInNF">Can I apply the
-GPL when writing a plug-in for a non-free program?</a></b></dt>
+GPL when writing a plug-in for a nonfree program?</a></b></dt>
<dd>
Please see this question <a href="#GPLPlugins">for determining when
@@ -1354,17 +1354,17 @@
and when they are considered separate programs</a>.
<p> If they form a
single combined program this means that combination of the GPL-covered
-plug-in with the non-free main program would violate the GPL. However,
+plug-in with the nonfree main program would violate the GPL. However,
you can resolve that legal problem by adding an exception to your
-plug-in's license, giving permission to link it with the non-free main
+plug-in's license, giving permission to link it with the nonfree main
program.</p>
<p>See also the question <a href="#FSWithNFLibs">I am
-writing free software that uses a non-free library.</a></p></dd>
+writing free software that uses a nonfree library.</a></p></dd>
<dt><b><a href="#TOCNFUseGPLPlugins" name="NFUseGPLPlugins">Can I
-release a non-free program that's designed to load a GPL-covered
+release a nonfree program that's designed to load a GPL-covered
plug-in?</a></b></dt>
<dd>
@@ -1381,7 +1381,7 @@
makes no requirements about the main program.</p>
<p>See also the question <a href="#FSWithNFLibs">I am
-writing free software that uses a non-free library.</a></p></dd>
+writing free software that uses a nonfree library.</a></p></dd>
<dt><b><a href="#TOCLinkingWithGPL" name="LinkingWithGPL">You have a
@@ -1620,8 +1620,8 @@
You cannot incorporate GPL-covered software in a proprietary system.
The goal of the GPL is to grant everyone the freedom to copy,
redistribute, understand, and modify a program. If you could
-incorporate GPL-covered software into a non-free system, it would have
-the effect of making the GPL-covered software non-free too.
+incorporate GPL-covered software into a nonfree system, it would have
+the effect of making the GPL-covered software nonfree too.
<p>
A system incorporating a GPL-covered program is an extended version of
that program. The GPL says that any extended version of the program
@@ -1632,7 +1632,7 @@
<p>
However, in many cases you can distribute the GPL-covered software
alongside your proprietary system. To do this validly, you must make
-sure that the free and non-free programs communicate at arms length,
+sure that the free and nonfree programs communicate at arms length,
that they are not combined in a way that would make them
effectively a single program.</p>
<p>
@@ -2172,7 +2172,7 @@
</dd>
<dt><b><a href="#TOCNonFreeTools" name="NonFreeTools">Can I release
- a program under the GPL which I developed using non-free
tools?</a></b></dt>
+ a program under the GPL which I developed using nonfree tools?</a></b></dt>
<dd>
Which programs you used to edit the source code, or to compile it, or
@@ -2180,7 +2180,7 @@
concerning the licensing of that source code.
<p>
-However, if you link non-free libraries with the source code, that
+However, if you link nonfree libraries with the source code, that
would be an issue you need to deal with. It does not preclude
releasing the source code under the GPL, but if the libraries don't
fit under the “system library” exception, you should affix
@@ -2331,7 +2331,7 @@
what their licenses are. Most system libraries either use
the <a href="/copyleft/lesser.html">GNU Lesser GPL</a>, or use the GNU
GPL plus an exception permitting linking the library with anything.
-These libraries can be used in non-free programs; but in the case of
+These libraries can be used in nonfree programs; but in the case of
the Lesser GPL, it does have some requirements you must follow.
<p>
Some libraries are released under the GNU GPL alone; you must use a
@@ -2482,7 +2482,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/10 21:22:40 $
+$Date: 2017/03/11 07:41:36 $
<!-- timestamp end -->
</p>
</div>