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
X-Info: This message was accepted for relay by
	smtp03.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: UmFuZG9tSVbobvek34daJZrLZGxoH2yCygRSJ3Xxm0adZKrTvTqNnxzOmqR/hdtj
Message-ID: <3EF25BA4.8060601@cygwin.com>
Date: Thu, 19 Jun 2003 20:56:04 -0400
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Marcel Telka <marcel AT telka DOT sk>
CC: cygwin AT cygwin DOT com
Subject: Re: Question about Cygwin License
References: <3E2D8043936AD611AF7D00508B5E9F4B45E45C AT server3 DOT mobilecom DOT com> <20030619221316 DOT GC7219 AT tortuga DOT etc DOT sk> <uznkdvg7o DOT fsf AT gnu DOT org> <20030619233820 DOT GF7219 AT tortuga DOT etc DOT sk>
In-Reply-To: <20030619233820.GF7219@tortuga.etc.sk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Marcel Telka wrote:

> 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?


Can I ask that we steer away from hypotheticals, at least on this
list?  We're talking about Cygwin and it's licenses.  You have a
choice of GPL, a compatible open-source license, or the "buy-out"
license (see <http://cygwin.com/licensing.html>).  Since these license
discussions can get tiresome quickly even when they stay on-topic, it's
best to keep as focused as possible.  The list appreciates your efforts
in this regard.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746


--
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/