public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: gnu-win32@cygnus.com
Subject: Re: Cygnus used in a Product ?
Date: Thu, 16 Oct 1997 03:16:00 -0000	[thread overview]
Message-ID: <199710160612.QAA05577@mundook.cs.mu.OZ.AU> (raw)
In-Reply-To: <3444D840.63B2@bbn.hp.com>

Claus Brod <claus_brod@bbn.hp.com> writes:

>desh wrote:
>> Anyone aware of any commercial application ported from UNIX to NT using
>> Cygnus ?
>> I would appreciate suggestion/Issues and experience related to porting a
>> commercial Unix based product on Windows NT.
>
>I'm not a licensing expert, but the license for the gnuwin32 stuff
>sounds as if you are required to ship source code for your app if it is
>based on gnuwin32 - I don't think that's acceptable for most commercial
>applications. But maybe I'm completely wrong on the licensing agreement?

Yes, you're wrong.

You don't need to ship source code unless your app is a "derivative work"
of the DLL, and if it just uses that standard POSIX interfaces it won't be.

Disclaimer: I do not represent Cygnus, I am not a lawyer,
this is not legal advice, yadda yadda yadda...

 | From fjh Fri Aug  8 19:00:24 1997
 | Subject: Re: [gnu-win32@cygnus.com] Revised licensing terms
 | To: win32@lists.debian.org (win32)
 | Date: Fri, 8 Aug 1997 19:00:24 +1000 (EST)
 | In-Reply-To: <m0wwEHJ-00IdTiC@golem.pixar.com> from Bruce Perens at "Aug 6, 97 03:10:00 pm"
 | 
 | > As long as they use a straight GPL as one of their licenses all of the
 | > tools will be OK with us, and only the library a problem. We could still
 | > work on a GLIBC 2.0 based library if we wished an LGPL platform.
 | 
 | There should be no need for that.  As far as I can see, commercial
 | software can still use cygwin.dll, so long as it is not a derivative
 | work.  And since cygwin.dll just provides a standard POSIX interface,
 | it would be very hard for Cygnus to argue that a commercial application
 | that made use of it was a derivative work.  (A Cygnus employee said as
 | much on the cygwin mailing list.)  Linking with the beta18 libcygwin.a
 | should be fine too, because they've declared that we can use beta18
 | under the terms of the Cygwin Licence, which basically says that
 | libcygwin.a can be used by anyone without any conditions applying.
 | 
 | Thus the only thing we need to do is to continue to provide a version
 | of libcygwin.a that can be used with commercial software and that
 | works with future releases of cygwin.dll.  Even that may be unnecessary.
 | 
 | Disclaimer: I'm not a lawyer, this is not legal advice, yadda yadda yadda...

--
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1997-10-16  3:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-14 23:13 desh
1997-10-15  7:51 ` Claus Brod
1997-10-16  3:16   ` Fergus Henderson [this message]
1997-10-17  9:51     ` Claus Brod
1997-10-18 12:23       ` Larry Meadows
1997-10-19  5:27         ` 
1997-10-19 13:47           ` Larry Meadows
1997-10-19 21:15         ` Fergus Henderson

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=199710160612.QAA05577@mundook.cs.mu.OZ.AU \
    --to=fjh@cs.mu.oz.au \
    --cc=gnu-win32@cygnus.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).