From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14511 invoked by alias); 14 Oct 2004 09:24:39 -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 7394 invoked from network); 14 Oct 2004 08:16:48 -0000 Message-ID: <416E35EB.4080106@chucker.rasdi.net> Date: Thu, 14 Oct 2004 09:24:00 -0000 From: Soeren Nils Kuklau User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-licensing@cygwin.com Subject: Bundling cygrunsrv with stand-alone projects Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-q4/txt/msg00000.txt.bz2 Hi, 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 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. I also found rather little documentation on `cygrunsrv'. The bundled README file comprehensively lists possible arguments, but appears to assume that the daemon to be run is inside the Cygwin root directory (such as C:\Cygwin), whereas we believe it would make more sense to distribute our package for installation inside Windows' Program Files folder. Does `cygrunsrv' understand Windows-like paths, or can we rely on a `/cygdrive/c/Program\ Files/'-like path structure? Thanks in advance for pointers, -- Soeren 'Chucker' Kuklau