From: "fergus" <fergus@bonhard.uklinux.net>
To: <cygwin-licensing@cygwin.com>
Cc: <fergus@bonhard.uklinux.net>
Subject: Licensing conditions: a question
Date: Wed, 18 Jan 2006 11:51:00 -0000 [thread overview]
Message-ID: <000001c61c1b$a6e3f5d0$500210ac@tcgp.dundee.ac.uk> (raw)
Please can you offer some guidance about the requirements of the supplier of
a piece of software that uses Cygwin to run?
Circumstance 1
==============
I am so good and kind that my software is free. Ask me for it and I'll give
it to you (or you can download it from my site) with instructions on how to
use it. By the way, it needs cygwin1.dll to run (and might or might not need
or at least benefit from other parts of the Cygwin provision, eg rxvt).
Requirement 1
=============
* make available the sources for the software
and one of
* invite interested parties to visit Cygwin to (minimal) get
cygwin1.dll or (more sophisticated) download and install some/ all of the
entire provision
or
* supply Cygwin setup and all sources on CD or DVD
Circumstance 2
==============
Almost identical to (1) except my software is not free: you can get it from
me in exchange for cash. As before, it needs cygwin1.dll to run (and might
or might not need or at least benefit from other parts of the Cygwin
provision, eg rxvt).
Requirement 2
=============
This is not at all clear to me. Is Requirement 2 unchanged from Requirement
1 or does the supplier have to engage in a legal contract with Cygwin
authorities, and does this contract entail the transfer of funds from said
supplier to said Cygwin authorities?
Thank you.
Fergus
next reply other threads:[~2006-01-18 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 11:51 fergus [this message]
2006-01-18 13:03 ` Corinna Vinschen
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='000001c61c1b$a6e3f5d0$500210ac@tcgp.dundee.ac.uk' \
--to=fergus@bonhard.uklinux.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).