From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Faylor To: Chris Telting Cc: Cygwin Mailing List Subject: Re: Cygwin licencing Date: Wed, 25 Aug 1999 09:08:00 -0000 Message-id: <19990825121020.B1508@cygnus.com> References: <002701beeefe$46dee830$e9c956d1@hercules> X-SW-Source: 1999-08/msg00670.html On Wed, Aug 25, 1999 at 06:32:27AM -0700, Chris Telting wrote: >I was reading an old thread in the archive and I'm a bit confused now about >the cygwin unix library licencing. I thought it was freely usable. But >then I read this in the faq: > > >In particular, if you intend to port a commercial (non-GPL'd) application >using Cygwin, you will need the commercial license to Cygwin that comes >with the supported native Win32 GNUPro product. The commercial license for >the Cygwin library is included in a GNUPro Toolkit subsciption. Pricing for >GNUPro Subscription starts at $6000 for three developers and includes GNUPro >Toolkit, Developer Support, and a commercial-use license for 100 copies of >the cygwin library. > > >I understand the library is GPL'd and not LGPL'd but if it's GPL how can >they can cygnus can be commercial licencers if there is code from other >contributers? The library is a dll and as such it's dynamicly linked. Can >anyone clarify this? We own 100% of the source code for the cygwin DLL. That means that we can relicense it as we please. Net releases are licensed under the GPL. Our commercial customers get a different license and are able to release the cygwin DLL without source code. If you have further questions about cygwin licensing, send mail to info@cygnus.com. Now, as Earnie suggested, it's best that this be discussed somewhere else besides this mailing list. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Faylor To: Chris Telting Cc: Cygwin Mailing List Subject: Re: Cygwin licencing Date: Tue, 31 Aug 1999 23:49:00 -0000 Message-ID: <19990825121020.B1508@cygnus.com> References: <002701beeefe$46dee830$e9c956d1@hercules> X-SW-Source: 1999-08n/msg00670.html Message-ID: <19990831234900.3IqDjqJ9NHDz90ma27kH_MjItLFdU4kYPnFaKs_1QI8@z> On Wed, Aug 25, 1999 at 06:32:27AM -0700, Chris Telting wrote: >I was reading an old thread in the archive and I'm a bit confused now about >the cygwin unix library licencing. I thought it was freely usable. But >then I read this in the faq: > > >In particular, if you intend to port a commercial (non-GPL'd) application >using Cygwin, you will need the commercial license to Cygwin that comes >with the supported native Win32 GNUPro product. The commercial license for >the Cygwin library is included in a GNUPro Toolkit subsciption. Pricing for >GNUPro Subscription starts at $6000 for three developers and includes GNUPro >Toolkit, Developer Support, and a commercial-use license for 100 copies of >the cygwin library. > > >I understand the library is GPL'd and not LGPL'd but if it's GPL how can >they can cygnus can be commercial licencers if there is code from other >contributers? The library is a dll and as such it's dynamicly linked. Can >anyone clarify this? We own 100% of the source code for the cygwin DLL. That means that we can relicense it as we please. Net releases are licensed under the GPL. Our commercial customers get a different license and are able to release the cygwin DLL without source code. If you have further questions about cygwin licensing, send mail to info@cygnus.com. Now, as Earnie suggested, it's best that this be discussed somewhere else besides this mailing list. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com