On Fri, Jun 20, 2003 at 12:35:00PM -0400, Sam Steingold wrote: >> * In message <[EMAIL PROTECTED]> >> * On the subject of "RE: cygwin license with windows apps?" >> * Sent on Fri, 20 Jun 2003 12:18:41 -0400 >> * Honorable Cary Lewis <[EMAIL PROTECTED]> writes: >> >> Why is it that linking to the cygwin.dll makes a program covered by GPL? > >because GPL says so: > >"This General Public License does not permit incorporating your program >into proprietary programs. If your program is a subroutine library, you >may consider it more useful to permit linking proprietary applications >with the library. If this is what you want to do, use the GNU Library >General Public License instead of this License." > >> On Linux systems, does linking to the open source 'C' libraries, >> etc. cause a program to be covered by the GPL? > >GNU GPL is _NOT_ GNU LGPL. >GNU libc (glibc) is under LGPL, not GPL. >cygwin is undef GPL, not LGPL. > >> I have trouble believing that there are systems out there that use >> cygwin in a commercial fashion that have not purchased the breakout >> license. > >"commercial fashion" != "proprietary fashion". > >those who _distribute_ _proprietary_ code linked with cygwin without >purchasing the breakout license are breaking the law. > >IANAL.
It's nice to see that some people get the concept at least. Thanks Sam and Elfyn. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
