From: Austin Ziegler Date: 2010-03-18T23:44:49+09:00 Subject: [ruby-core:28754] Re: [Bug #2982] Ruby tries to link with both openssl and readline On Thu, Mar 18, 2010 at 5:37 AM, Lucas Nussbaum wrote: > On 18/03/10 at 18:23 +0900, Yukihiro Matsumoto wrote: >> In message "Re: [ruby-core:28735] [Bug #2982] Ruby tries to link with both openssl and readline" >> � � on Thu, 18 Mar 2010 17:01:38 +0900, Lucas Nussbaum writes: >> |Ruby currently tries to link with both OpenSSL (which is under the SSL license), and Readline (GPL). >> >> No. �The Ruby does not try to link with those libraries by default, >> unless explicitly required by the user, so that it is a user's >> responsibility to avoid loading those two in the same address space. > > Users, and developers of third-party libraries and application. Note > that it is de-facto illegal to use openssl with GPL libraries/gems (and > there are quite a lot of GPL-only libraries/gems). This is completely incorrect and FUD. It is against the license to *distribute* GNU GPL libraries/gems with OpenSSL. There is nothing against the license for use. The GNU GPL is a distribution license, not a EULA. If end users do something but do not distribute that something, it's not illegal. The FSF also takes a maximal view on shared libraries that is not so far supported by any court case or common sense. It is perfectly legal to ship a GNU GPLed Photoshop plug-in, and it is perfectly legal for a user to use such. RMS and the FSF do not believe so, but the only court cases that talk about in-memory copies indicate that they are a necessary by-product of running the program, and as such it's not a problem. Please stop the GPL zealot's FUD. -austin -- Austin Ziegler � halostatue@gmail.com � austin@halostatue.ca http://www.halostatue.ca/ � http://twitter.com/halostatue