From: DJ Delorie <dj@delorie.com>
To: dwyatt@sunflower.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Things you can do with Cygwin
Date: Tue, 02 May 2000 08:55:00 -0000 [thread overview]
Message-ID: <200005021555.LAA20541@envy.delorie.com> (raw)
In-Reply-To: <200005030139.UAA00749@mail1.sunflower.com>
> I'm still not clear on something. Can a proprietary,
> non-open-source software package be ported to run under Cygwin and
> then sold to customers if, say, a copy of the CD release is
> purchased and included for every host that the software will run on?
> Or, would this require the purchase of the Cygwin developer package
It doesn't matter which version of cygwin you have, or where you got
it from, or how much you paid for it. If you want to distribute a
proprietary application that uses Cygwin, you need to purchase a
proprietary-use license. If you want to distribute an "open source"
application that uses Cygwin, you don't need to purchase anything.
Note that I said "distribute", not "write". You can always write any
application you want, if you only use it yourself (or within your
company, if it's a company-written application), because you aren't
distributing those. You meet the terms of the GPL if you don't
distribute your program, regardless of any other license terms it has.
> (I can't find the link for that, at the moment - the Web site seems
> to have been partially absorbed into Red Hat)?
Send email to cygwin-info@cygnus.com if you are interested in the
proprietary-use license. The commercial URL for cygwin is
http://www.cygnus.com/cygwin/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-05-02 8:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-01 20:22 DJ Delorie
2000-05-02 5:42 ` Doug Wyatt
2000-05-02 8:55 ` DJ Delorie [this message]
2000-05-02 10:42 ` Charles Hixson
2000-05-02 11:20 ` DJ Delorie
2000-05-02 12:29 ` Kendall Bennett
2000-05-02 12:45 ` DJ Delorie
2000-05-02 12:57 ` Mo DeJong
2000-05-02 13:20 ` DJ Delorie
2000-05-03 8:31 ` Charles Hixson
2000-05-03 8:50 ` Larry Hall (RFK Partners, Inc)
2000-05-03 9:23 ` DJ Delorie
2000-05-02 13:38 ` Kendall Bennett
2000-05-02 16:34 ` DJ Delorie
2000-05-02 17:08 ` Suhaib M. Siddiqi
2000-05-02 12:30 ` Norman Vine
2000-05-02 12:53 ` DJ Delorie
2000-05-02 13:16 ` Norman Vine
2000-05-02 13:32 ` DJ Delorie
2000-05-02 5:09 Earnie Boyd
2000-05-03 1:59 Bernard Dautrevaux
2000-05-03 5:05 ` DJ Delorie
2000-05-03 7:33 13mb80000-HallM(10053584)37x10
2000-05-03 7:47 ` DJ Delorie
2000-05-03 8:05 13mb80000-HallM(10053584)37x10
2000-05-03 8:09 ` DJ Delorie
2000-05-03 8:23 ` David Lane
2000-05-03 9:19 David Robinow
2000-05-03 10:45 Earnie Boyd
2000-05-03 11:04 ` Larry Hall (RFK Partners, Inc)
2000-05-03 11:33 ` Chris Faylor
2000-05-03 11:53 David Robinow
2000-05-03 11:59 ` Chris Faylor
2000-05-03 21:34 Bernard Dautrevaux
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=200005021555.LAA20541@envy.delorie.com \
--to=dj@delorie.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=dwyatt@sunflower.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).