** Summary **

'''GPL''' is An acronym for the [GNU] '''G'''eneral '''P'''ublic
[license%|%License], a family of software licenses that are common among
FSF developers and many others; 


** See Also **

    [LGPL]:   

    [GPL Scripts]:   the implications of releasing a Tcl script under GPL

    [https://groups.google.com/forum/#!searchin/comp.lang.tcl/andreas$20otto/comp.lang.tcl/_Kcibui3DI0/9khh-3fpb8QJ%|%ANN: CriTcl 0.18 builds C extensions on-the-fly] ,[comp.lang.tcl] ,2001-11-12:   a long thread that ended up discussing the merits of the GPL

    [https://groups.google.com/forum/#!searchin/comp.lang.tcl/gpl%|%Google search for "GPL"] [comp.lang.tcl]:   


** Reading **

   [http://www.gnu.org/licenses/gpl-faq.html%|%GPL FAQ]:   official [FAQ]'s

   [http://www.gnu.org/licenses/quick-guide-gplv3.html%|%compatibility overview GPL v3]:   

   [http://www.gnu.org/licenses/gpl-1.0.html%|%GPL v1 (1989) license text]:   

   [http://www.gnu.org/licenses/gpl-2.0.html%|%GPL v2 (1991) license text]:   

   [http://www.gnu.org/licenses/gpl-3.0.html%|%GPL v3 (2007) license text]:   

   [http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/doc/Why-CLISP-is-under-GPL%|%Common Lisp and Readline], clisp mailing list, 1992-10-19


** Description **

However it is not at all favoured for the Tcl core, as it severely restricts
what commercial development may be done with it.  IMHO it works better for
applications, and though there is the [LGPL] (Lesser or Library GPL) and other
derivative FSF-sponsored licenses to address these sorts of concerns, Tcl's
modified Berkeley license is still the currently preferred (and required for
Tcl core work) license.

<<categories>> Category Glossary | Category Licence