Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20040615182616.03288008@pop.prospeed.net>
X-Sender: 
Date: Tue, 15 Jun 2004 18:29:20 -0400
To: Britton Kerin <bkerin AT asf DOT alaska DOT edu>, Cygwin List <cygwin AT cygwin DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: is it ok to ship cygwin.dll with an application covered by BSD?
In-Reply-To: <Pine.LNX.4.44.0406151424370.12717-100000@mail1.asf.alaska. edu>
References: <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040615155121 DOT 03291398 AT pop DOT prospeed DOT net> <Pine DOT LNX DOT 4 DOT 44 DOT 0406151424370 DOT 12717-100000 AT mail1 DOT asf DOT alaska DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Yikes!  I didn't proofread my response very well.  Must have gotten
caught by cross-VNC copy-paste trouble. :-(

This is the link I meant to send <http://cygwin.com/licensing.html>.
Really. :-)

Sorry for the confusion.

Larry

At 06:25 PM 6/15/2004, you wrote:

>I've looked at the FAQ ("What are the copyrights?" section) and other 
>places, if you are saying that my question is bad or already answered.
>
>Britton Kerin
>
>On Tue, 15 Jun 2004, Larry Hall wrote:
>
>> At 03:00 PM 6/15/2004, you wrote:
>> 
>> >We have a free radar processing system for which we are trying to release
>> >a windows version.  We have obtained permission from our university to
>> >release our code under the BSD license.  We would be happy to choose the
>> >GPL, but the lunatic whims of those in charge seem inflexible in this
>> >case.  We have tried hard to get the system going using mingwin and the
>> >cygwin.a library, which we understand is ok to use, but it doesn't quite 
>> >work, some important libraries fail to build.  With cygwin.dll, 
>> >everything is beautiful.  
>> >
>> >I'm not clear if we are allowed to ship the application with cygwin.dll
>> >though.  We could include source code for cygwin.dll, or source code
>> >pointers, or whatever.  I am hoping that since cygwin.dll is freely
>> >available, we can ship it with our processor?
>> >
>> >Thanks for any information you can provide,
>> >Britton Kerin
>> 
>> 
>> I'd recommend checking out <http://cygwin.com/problems.html>, especially
>> the "note" at the bottom.  My quick review would suggest that this is the
>> important part as far as you're concerned.
>> 
>> 
>> 
>> 
>> --
>> 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/ 


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