chiark / gitweb /
src/types.c: Do not crash when one of several addr subqueries fails
[adns] / GPL-vs-LGPL
CommitLineData
71ede3cd 1 GPL vs LGPL, in the context of adns
2 -----------------------------------
3
239d2e4d 4Several people have asked me to release GNU adns under the GNU Lesser
71ede3cd 5General Public Licence (LGPL, formerly the Library GPL) instead of the
6`stronger' GPL. This file is intended to answer most of these
7questions. If you still have questions or comments, please mail me at
8<adns-maint@chiark.greenend.org.uk>.
9
10Typically there are two or three kinds of situation where people make
a14bea78 11this request: the first is where another free software project
12currently using a GPL-incompatible licence, wishes to use adns. The
13second case, which often overlaps with the first, is where a free
14software project is currently using an MIT-like licence or the LGPL
15and fear `GPL infection'. The third case is where someone is
16developing a proprietary program and wishes to make use of adns but
17doesn't wish to make their program free software
71ede3cd 18
19
a14bea78 201. GPL-incompatible free software licences
21------------------------------------------
71ede3cd 22
a14bea78 23Regrettably, there are a number of free software licences (and
24semi-free licences) in existence which are not compatible with the
25GPL. That is, they impose restrictions which are not present in the
26GPL, and therefore distributing a whole work which contains both such
27a program and a GPL'd program is not possible: either the combination
28would have to be distributed under the GPL (violating the restrictions
29made by the original author), or under the GPL-incompatible licence
30(violating the GPL).
71ede3cd 31
a14bea78 32I may be prepared to make exceptions for such a licence. Please
33contact me at <adns-maint@chiark.greenend.org.uk> with the full text
34of the GPL-incompatible licence. However, I would usually prefer it
35if you could use a GPL-compatible licence for your project instead.
71ede3cd 36
71ede3cd 37
382. GPL-avoiding projects (MIT licence, et al)
39---------------------------------------------
40
41Some free software projects prefer to avoid the GPL and other licences
42which force the software always to be free. Instead they use
43something like the MIT X licence, which allows proprietary versions of
239d2e4d 44their software, or the in the case of some free libraries, the LGPL,
45which allows proprietary applications. I have to say that I think
46these people are misguided, but that doesn't mean that they don't have
47a perfect right to do that.
71ede3cd 48
49Some of these people think that merely writing to an interface
50provided by GPL'd software will cause their program to become GPL'd
51too, even if they don't distribute the GPL'd software. I don't think
239d2e4d 52this is the case. I'm perfectly happy for non-GPL'd but
53GPL-compatible software to refer to adns in its source code. However,
54I think that exectuables (or compiled libraries) which contain or are
55dynamically linked against adns must be GPL'd; likewise executable
56programs (whether compiled or in an interpreted language) which
57require utilities from adns to function properly must be GPL'd.
58
59So, you can distribute your non-GPL'd program source which needs adns
60to compile (provided it's under a GPL-compatible licence), but people
61who wish to distribute binaries must do so under the terms of the GNU
62GPL. This may make sense for some GPL-avoiding free software
63projects; people can still make proprietary programs from your code,
64provided that they make some provision to replace adns with something
65whose copyright allows proprietary versions.
66
67However, this doesn't make much sense for the authors of LGPL'd
68libraries. All I can say to them is to ask which is more important:
69that their library be well-constructed and use all the best technology
70available as free software, or whether it is worth degrading quality
71of their library in order to allow proprietary programs to use it !
72
73To help the case of LGPL'd libraries for which adns is not a vital
74component - for example, a library which provides access to other
75libraries so that programs which use it need only use certain parts,
76I have released adns.h (just the public header file) under the LGPL as
77well as the GPL. See the copyright notice in adns.h for details.
78Note that this will not help you if it adns is essential to the
79functioning of your library, because all programs using your library
80must link against both your library and adns and so must be GPL'd.
81
82
83For some information and views from the Free Software Foundation on
84free software licensing, visit:
85
86 Various licenses and comments about them
87 at http://www.fsf.org/philosophy/license-list.html
88
89 Why you shouldn't use the Library GPL for your next library
90 at http://www.fsf.org/philosophy/why-not-lgpl.html
71ede3cd 91
92
71ede3cd 93Local variables:
94mode: text
95End: