This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Licensing Issues?
- To: "David A. Cobb" <superbiskit at home dot com>
- Subject: Re: Licensing Issues?
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- Date: Wed, 12 Sep 2001 18:06:36 -0400
- CC: Cygwin Library General Discussion <cygwin at cygwin dot com>,NewLib Discussion <newlib at sources dot redhat dot com>
- References: <3B9FD58F.7000308@home.com>
David A. Cobb wrote:
> Would someone in the know please explain why there are licensing issues
> between GLibC and Newlib? Are they not both GPL?
>
Sigh. this has been explained so many times I am surprised your search
of the archives did not reveal it. You *did* search the archives, right?
Cygnus (now Red Hat) releases cygwin under two licenses: the GPL and a
proprietary license. People who purchase cygwin under the proprietary
license are allowed to distribute cygwin-based binaries WITHOUT
distributing their source code. (You may not like this arrangement, but
it's the way things are. Besides, the proceeds pay Chris' and Corinna's
and others' salaries...)
Anyway, ONLY the copyright owner of a particular work is allowed to
establish the license terms. If you take GPL code that you do not own,
you can't change the license -- although the GPL gives you certain
redistribution rights.
Since Red Hat needs to specify the license, they need to own the code.
They don't own the glibc code. Therefore they can't use it (as part of
cygwin1.dll -- e.g. newlib) [This also explains why everybody who
contributes to cgywin1.dll must sign over copyright to Red Hat].
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/