Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 20 Jun 2003 01:38:20 +0200
From:	Marcel Telka <marcel AT telka DOT sk>
To:	cygwin AT cygwin DOT com
Subject:	Re: Question about Cygwin License
Message-ID:	<20030619233820.GF7219@tortuga.etc.sk>
References:	<3E2D8043936AD611AF7D00508B5E9F4B45E45C AT server3 DOT mobilecom DOT com> <20030619221316 DOT GC7219 AT tortuga DOT etc DOT sk> <uznkdvg7o DOT fsf AT gnu DOT org>
Mime-Version:	1.0
In-Reply-To:	<uznkdvg7o.fsf@gnu.org>
User-Agent:	Mutt/1.4.1i

On Thu, Jun 19, 2003 at 06:46:03PM -0400, Sam Steingold wrote:
> > * Honorable Marcel Telka <marcel AT telka DOT sk> writes:
> >
> > On Thu, Jun 19, 2003 at 05:51:44PM -0400, Cary Lewis wrote:
> > > I want to use cygwin with a proprietary system. 
> > > 
> > > As I do not want to publish my source code, I know I need a "breakout"
> > > license from RedHat.
> > > 
> > > I am not changing cygwin, I am simply using the cygwin.dll to get a Unix 
> > > based system to run under Windows.
> > 
> > Cite from GNU GPL <http://www.gnu.org/licenses/gpl.html>:
> > 
> > Activities other than copying, distribution and modification are not
> > covered by this License; they are outside its scope. The act of
> > running the Program is not restricted, and the output from the Program
> > is covered only if its contents constitute a work based on the Program
> > (independent of having been made by running the Program). Whether that
> > is true depends on what the Program does.
> 
> linking against a GNU GPL (not LGPL!) library makes your program GPL,
> even if the library is dynamic (DLL).
> 
> <http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/clisp/clisp/doc/Why-CLISP-is-under-GPL?rev=HEAD>
> 
> therefore, if you distribute a program which relies on cygwin.dll
> (which, IIUC, is released under the GNU GPL), you have to either

What about this situation?

My program depends on cygwin.dll, but there are two implementations of the
library: one with GNU/GPL license and another one with, say, BSD-like
license.

Should I (in this situation) release my program under GNU/GPL terms?

> release the source code under GNU GPL, or buy a different license from
> the (C) holder (RedHat).
> 
> IANAL.

-- 
+-------------------------------------------+
| Marcel Telka   e-mail:   marcel AT telka DOT sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel AT jabber DOT sk |
+-------------------------------------------+

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -