From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: Licensing/Installer Questions
Date: Wed, 01 Mar 2006 10:02:00 -0000 [thread overview]
Message-ID: <20060301095501.GK3184@calimero.vinschen.de> (raw)
In-Reply-To: <3816256.1141199172470.JavaMail.chartpacs@mac.com>
On Mar 1 02:46, Michael Banks wrote:
> Hello,
>
> Our company has released a commercial product for the medical industry
> called SpongePACS ( http://www.spongepacs.com ). It was developed in a
> database program called FileMaker Pro, which has the ability to access
> the command line. In fact, SpongePACS relies heavily on utilities like
> grep and find, which come with a standard installation of Mac OS X.
>
> Since we want to also target the larger Windows user base, we need to
> find Windows equivalents, and Cygwin has worked fine in our testing,
> but I have a couple of questions:
>
> 1) Licensing. I've read the licensing pages, but I'm still confused.
> We're not porting a Unix/Linux application to Windows. All we need are
> a dozen or so packages (mainly from the Base category, plus a few
> others). Do we still need to purchase a special Cygwin license from
> Red Hat?
The Cygwin buy-out license covers the case in which a proprietary
application is linked against Cygwin and should stay proprietary. In
this case you have to purchase the license.
If your closed-source applications are not linked against Cygwin, or if
you decide to convert the license of your product to a blessed open-
source license, then you don't have to purchase the Cygwin buy-out
license.
If Cygwin is only used for open-source tools which are packed with
your applications, then that's fine. But see below.
> 2) Installer. As I mentioned before, SpongePACS is a product for the
> medical industry. Believe it or not, many doctors' offices do *not*
> have an Internet connection, so can we bundle a Cygwin installer that
> just has the needed packages, and include this installer on a CD with
> our product?
Whatever you do, please keep in mind that you have to provide the full
sources of Cygwin and all accompaning open-source tools. If you fail to
give your customers the source codes, you're infringing the license.
HTH,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2006-03-01 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 9:17 Michael Banks
2006-03-01 10:02 ` Corinna Vinschen [this message]
2006-03-01 14:05 ` Michael Banks
2006-03-01 14:19 ` Corinna Vinschen
2006-03-03 12:17 ` Michael Banks
2006-03-03 13:01 ` Corinna Vinschen
2006-03-03 15:51 ` Dave Korn
2006-03-03 15:32 ` Dave Korn
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=20060301095501.GK3184@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).