From: "James, Roshan (Cognizant)" Date: 2004-04-28T02:11:58+09:00 Subject: Re: Distributing Ruby DLL ------=_NextPartTM-000-c2a9faad-25a1-4b8a-906a-da2b9407bb50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable //I think everything above is wrong. //a GPL DLL definitely puts the calling code under the the GPL.=20 //Thats why we have LGPL and GPL. Some people (the MySQL=20 //company) think that even connections with sockets to a GPL=20 //server makes the client application to fall under the GPL. I=20 //believe that this is absolute nonsense, but at the moment it=20 //is a good FUD strategy and a reason to boycott MySQL. I am just curious about how this would work then - if I do=20 LoadLibrary("somefile.dll") in my code and the licensing of a=20 generally available "somefile.dll" became GPL code, it affects the=20 licensing of my program?=20 So any program on a linux machine, that uses any .so that is=20 under the GPL becomes GPLed ?=20 Isnt that a *little* harsh? I thought it applied to only source=20 level linkages and modifications (or derivate works).=20 //Your understanding is essentially correct, with a couple of important=20 //caveats: // //1. The FSF does not agree. //2. US case law appears to mostly agree, but it is not=20 //entirely settled. 3. Other jurisdictions may deal with this=20 //differently. Thank you Austin - I was personally considering building some free code (free not as in FSF (c)Free, but free as in generally-=20 lying-around-without-a-license-for-everyone-to-use-free) that uses Ruby as the major ingredient in the config script.=20 If this restriction applies, then I'd be forced not to use ruby because I would like a company to be able to make money out of=20 my work and and keep their work proprietary or not at their option,=20 rather than my dictation. =20 Roshan http://pensieve.thinkingms.com/ ------=_NextPartTM-000-c2a9faad-25a1-4b8a-906a-da2b9407bb50 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com ------=_NextPartTM-000-c2a9faad-25a1-4b8a-906a-da2b9407bb50--