This is the mail archive of the
mailing list for the Cygwin project.
Re: Licensing question
- To: Jim dot Fairchild at IndSys dot ge dot com, cygwin at sourceware dot cygnus dot com
- Subject: Re: Licensing question
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Wed, 20 Oct 1999 12:39:06 -0700 (PDT)
- Reply-To: earnie_boyd at yahoo dot com
--- Jim.Fairchild@IndSys.ge.com wrote:
> I have a question regarding the statement, "if you intend to port a
> (non-GPL'd) application using Cygwin, you will need the commercial license to
> Cygwin that comes with the supported native Win32 GNUPro product". What
> licensing restrictions apply if you plan on using the Unix utilities only,
> will not be developing applications that use the cygwin? The Unix utilities
> would be used in a commercial application to enable the customer to
> from a UNIX system to a Windows NT system.
Notice: This is _not_ Legal Advice. I shall not be held liable for damages
caused by this response.
IMO, your use of a GPL binary does not cause your commercial package problems.
If you include a GPL library in your commercial package such as libreadline.a
then your package must then also be covered by the GPL.
If you distribute a GPL binary then YOU must agree to have the source available
upon request for three years after the distribution for the version of the
binary distributed or also distribute the source when you distribute the
Please, refer to the COPYING document at the http://www.fsf.org site or should
be found with any GPL distribution. It _is_ the legal document for the GPL.
Earnie Boyd <mailto:email@example.com>
Newbies, please visit
(If you respond to the list, then please don't cc me)
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org