public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.edu>
To: mvoss@kuttig.com
Cc: gnu-win32@cygnus.com
Subject: Re: Licensing Terms
Date: Fri, 06 Nov 1998 15:02:00 -0000	[thread overview]
Message-ID: <9811062154.AA10047@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <C12566B3.00317331.00@notes.kuttig.com>

mvoss@kuttig.com writes:
> 
> Does that also apply to software built with EGCS-1.1-MinGW32 ???
> If so, WHAT do I have to buy, and what share does Mumit Khan get of that
> money (he made the MinGW324EGCS package, after all)?

No, it does not apply to software built with EGCS-1.1-Mingw. Cygwin and 
Mingw are completely independent as far as copyrights and licensing issues 
are concerned.

Mingw itself (runtime and the include files etc) explicitly not
copyrighted (by Colin Peters or by anybody else). The egcs-1.1 components 
have various different copyrights/licenses, and it's the same as on any 
Unix system.

> Can I SELL the software built with either Cygwin or EGCS if I include the
> source code?

You can do anything you want with Mingw/egcs built software. As for
software built with Cygwin EGCS, you can always SELL the software as 
long as you comply with the license that comes with Cygwin.

Regards,
Mumit

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  parent reply	other threads:[~1998-11-06 15:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-05  0:56 mvoss
1998-11-06  9:01 ` DJ Delorie
1998-11-06 15:02 ` Mumit Khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-01  7:37 Licensing terms Clark, Matthew C (FL51)
2001-08-02 11:39 ` Christopher Faylor
2001-08-01  5:52 Clark, Matthew C (FL51)
2001-08-01  6:17 ` Corinna Vinschen
2001-08-01  6:26   ` Steve Lhomme
2001-08-01  6:49     ` Corinna Vinschen
2001-08-01  7:34   ` Charles Wilson
2000-08-08  8:48 licensing terms NOE Nicolas
2000-08-08  9:04 ` DJ Delorie
2000-08-08  9:24   ` John McClenning
2000-08-08  9:33     ` DJ Delorie
2000-08-08  9:39       ` Chris Faylor
     [not found] <363DE24C.EDC9B967.cygnus.gnu-win32@solidum.com>
1998-11-04  4:32 ` Licensing Terms DJ Delorie
1998-11-05  6:50   ` zigweidr
1998-11-07  0:01     ` Stephen Vance
     [not found] ` <364353BD.72F1F658.cygnus.gnu-win32@deneb.com>
1998-11-08  2:27   ` DJ Delorie
1998-11-02 17:57 Van Murray

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=9811062154.AA10047@modi.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=gnu-win32@cygnus.com \
    --cc=mvoss@kuttig.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).