Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Tue, 2 May 2000 14:19:49 -0400
Message-Id: <200005021819.OAA21633@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: charleshixsn AT earthlink DOT net
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <390F1363.A145F514@earthlink.net> (message from Charles Hixson on
	Tue, 02 May 2000 10:41:55 -0700)
Subject: Re: Things you can do with Cygwin
References: <200005030139 DOT UAA00749 AT mail1 DOT sunflower DOT com> <200005021555 DOT LAA20541 AT envy DOT delorie DOT com> <390F1363 DOT A145F514 AT earthlink DOT net>


> Actually, I think it's even a bit less restrictive than that.  I
> believe that you can sell an application that depends on CygWin,
> even as a closed-source proprietary program.

No, this is just plain wrong.  When you build an application with
cygwin, part of cygwin itself is statically linked into the
application.  The application is GPL at that point.

> saying that YOU can't distribute the GPL'd software that your
> closed-proprietary application depends on, but you can tell the user
> where to get it.

"Making it available" and "distributing it" are the same thing.
Putting a file up for ftp and letting a user copy it to their own
machine is no different than putting it on a floppy and letting the
user copy it off the floppy.  The only time it's not a distribution is
if the recipient broke into the user's machine and stole it against
the user's will.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com