JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Switching the Cygwin DLL to LGPLv3+, dropping commercial buyout option

Browse Source 
Bump GPLv2+ to GPLv3+ for some files, clarify BSD 2-clause.

Everything else stays under GPLv3+.

New Linking Exception exempts resulting executables from LGPLv3 section 4.

Add CONTRIBUTORS file to keep track of licensing.

Remove 'Copyright Red Hat Inc' comments.

Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
This commit is contained in:
Corinna Vinschen
2016-05-24 11:16:39 +02:00
parent 94e3a561d0
commit 6e623e9320
408 changed files with 342 additions and 1048 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
winsup/doc/faq-using.xml
View File

@@ -572,13 +572,15 @@ contributing it for others to use)
Can I bundle Cygwin with my product for free?
</para></question>
<answer><para>
Only if you comply with Cygwin's <ulink
url="https://cygwin.com/licensing.html">license</ulink> very carefully. If you
choose to distribute cygwin1.dll, you must be willing to distribute the
exact source code used to build that copy of cygwin1.dll as per the
terms of the GPL. If you ship applications that link with cygwin1.dll,
you must either provide those applications' source code under a
GPL-compatible license, *or* purchase a cygwin license from Red Hat.
Starting with Cygwin version 2.5.2, which is LGPL licensed, yes, albeit
it's not recommended for interoperability reasons.</para>
<para>Cygwin versions prior to 2.5.2 were GPL licensed.
If you choose to distribute an older cygwin1.dll, you must be willing to
distribute the exact source code used to build that copy of cygwin1.dll
as per the terms of the GPL. If you ship applications that link with
older cygwin1.dll, you must provide those applications' source code
under a GPL-compatible license.
</para></answer></qandaentry>
<qandaentry id="faq.using.older-cygwin-conflict">