From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26644 invoked by alias); 14 Oct 2004 16:15:56 -0000 Mailing-List: contact cygwin-licensing-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-licensing-owner@cygwin.com Received: (qmail 26632 invoked from network); 14 Oct 2004 16:15:55 -0000 Received: from unknown (HELO slinky.cs.nyu.edu) (128.122.20.14) by sourceware.org with SMTP; 14 Oct 2004 16:15:55 -0000 Received: from localhost (localhost [127.0.0.1]) by slinky.cs.nyu.edu (8.12.10+Sun/8.12.10) with ESMTP id i9EGFsoQ026843 for ; Thu, 14 Oct 2004 12:15:54 -0400 (EDT) Date: Thu, 14 Oct 2004 16:15:00 -0000 From: Igor Pechtchanski Reply-To: cygwin-licensing@cygwin.com To: cygwin-licensing@cygwin.com Subject: Re: Bundling cygrunsrv with stand-alone projects In-Reply-To: <20041014103502.GL6702@cygbert.vinschen.de> Message-ID: References: <416E35EB.4080106@chucker.rasdi.net> <20041014103502.GL6702@cygbert.vinschen.de> Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 X-IsSubscribed: yes X-SW-Source: 2004-q4/txt/msg00002.txt.bz2 On Thu, 14 Oct 2004, Corinna Vinschen wrote: > On Oct 14 10:16, Soeren Nils Kuklau wrote: > > we're working on a cross-platform server daemon which on Windows gets > > compiled through Cygwin. To make installation convenient for Windows > > users, we would like to bundle `cygwin1.dll' and the necessary files for > > `cygrunsrv' with our Windows port. Before we try and implement that on > > Why? You know that you create a couple of problems for users who already > have installed Cygwin on their machines? > [snip] > > > our side, however, we would like to know about the licensing implications. > > > > The project is `non-commercial' (as in 1) our primary purpose isn't to > > make big bucks off it and 2) it is available for download at no cost) > > and `open-source' (as in there's an issue tracker, and we will probably > > allow anonymous SVN access to the source as the project becomes more > > stable), but not under a GPL-compatible license. > > The secret word is "GPL". It doesn't matter if you want to make money > with it as long as you release your source code under an Open-Source > compliant license according to the following definition: > > http://www.opensource.org/docs/definition_plain.html > > If your software doesn't meet these criterias, you will have to buy > a buy-out license from Red Hat, see http://cygwin.com/licensing.html Hmm, I may be opening a can of worms here, but doesn't GPL allow bundling GPL'd binaries with other binaries that aren't GPL-compatible (or even open-sourced) as long as they aren't linked together? At least, that's what the "mere aggregation" clause covers -- see () and . > Please note that when you're distributing binary versions of Cygwin and > cygrunsrv, you also have to provide the sources from which the Cygwin > and cygrunsrv versions have been built to comply with the GPL. You must > not rely on Red Hat keeping the sources of these versions for you. Yes. The GPL FAQ is a good read in any case -- perhaps the first message on this list should've pointed people to it... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing." -- Dr. Jubal Harshaw