From: Soeren Nils Kuklau <cygwin@chucker.rasdi.net>
To: cygwin-licensing@cygwin.com
Subject: Bundling cygrunsrv with stand-alone projects
Date: Thu, 14 Oct 2004 09:24:00 -0000 [thread overview]
Message-ID: <416E35EB.4080106@chucker.rasdi.net> (raw)
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
next reply other threads:[~2004-10-14 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 9:24 Soeren Nils Kuklau [this message]
2004-10-14 11:15 ` Corinna Vinschen
2004-10-14 16:15 ` Igor Pechtchanski
2004-10-14 17:03 ` Christopher Faylor
2004-10-14 17:12 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416E35EB.4080106@chucker.rasdi.net \
--to=cygwin@chucker.rasdi.net \
--cc=cygwin-licensing@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).