Re: [Sablevm-developer] Declaring SableVM ported to Windows... tomorrow ;-)
Brought to you by:
egagnon
From: Grzegorz B. P. <ga...@de...> - 2004-01-17 22:31:21
|
W liście z sob, 17-01-2004, godz. 17:07, Chris Pickett pisze: > Well, I read it as this: the libsablevm.dll can be created and > distributed under the LGPL, but you need cygwin1.dll to run. If you > modify cygwin1.dll and distribute the changes, it must be done under the > GPL. > > Just provide two downloads -- one for SableVM, with source, licensed > under the LGPL, and one for cygwin1.dll, with source, licensed under the > GPL. If the cygwin1.dll source isn't part of the sablevm tree then I > don't see the problem. However, if you don't want to host the cygwin > source but just the unmodified .dll, I *think* that's okay -- as long as > you meet section 3b or 3c of the GPL (the written offer for 3 years does > not necessarily imply having it available for download without even > asking, if I read it correctly). > > I don't think they would make the exception to allow you to build an > LGPL'd .dll if the resulting program was GPL'd automatically at runtime > just because you're forced to link to cygwin1.dll. That's misleading > and I don't think Cygwin is out to mislead people. I think you read it right. Mostly. I still have this issue here. See this: If running a java program on a JVM means linking to the JVM, then the java program links to cygwin.a too (let alone .dll). But the the exception is for OpenSource(tm) programs only. Though if the java program is not OpenSource(tm) licensed then we're not allowed to use the exception, so we fall under the GPL and we're not allowed to run this non-OpenSource(tm) program. It means that on SableVM on Cygwin we can run GPL-incompatible programs, BUT they have to be OpenSource(tm). So... anybody to polish the SableVM Cygwin port? :-) I'd be glad to help. Grzegorz B. Prokopski -- Grzegorz B. Prokopski <ga...@de...> Debian GNU/Linux http://www.debian.org SableVM - LGPLed JVM http://www.sablevm.org |