delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/09/12/18:07:10

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B9FDC6C.2000502@ece.gatech.edu>
Date: Wed, 12 Sep 2001 18:06:36 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: "David A. Cobb" <superbiskit AT home DOT com>
CC: Cygwin Library General Discussion <cygwin AT cygwin DOT com>,
NewLib Discussion <newlib AT sources DOT redhat DOT com>
Subject: Re: Licensing Issues?
References: <3B9FD58F DOT 7000308 AT home DOT 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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019