From: Ray Cote <rgacote@...>
Date: 2003-07-09T09:35:47+09:00
Subject: Re: My brief and torrid affair with Ruby.

At 9:08 AM +0900 7/9/03, Daniel Carrera wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Wed, Jul 09, 2003 at 08:57:58AM +0900, Ray Cote wrote:
>
>>  Specifically, I just happened to look at the source code in DBI.rb
>>  and Oracle.rb and was astonished to discover that these modules are
>>  GPL. Then I quickly found trace.rb, and proxy.rb were GPL as well.
>
>Well... since you are not linking or modifying the source code of 
>these files I
>would suppose that the GPL doesn't affect you at all.  You are still 
>able to make
>your own propietary program and use these external files.

Hi Daniel:
Thanks for your comments.

I believe these two items from the GPL FAQ cover the question:
<http://www.gnu.org/licenses/gpl-faq.html#WhyUseGPL>

---
If a library   is released under the GPL (not the LGPL), does that 
mean that any   program which uses it has to be under the GPL?
Yes, because the program as it is actually run includes the library
---
You have a   GPL'ed program that I'd like to link with my code to 
build a   proprietary program.  Does the fact that I link with your 
program mean   I have to GPL my program?
Yes.
---

>Secondly, even if it *is* a derivative work, you can still make propietary
>programs for your own company (but not for your clients).
Correct. I was referring to products we build and distribute to customers.

>Finally, who does making your program open source inhibit you from making it
>commercial?  I mean, if you are currently using Perl and Python you 
>are certainly
>not hiding the source code.  You can't!  What's the problem with selling a
>GPL-covered application?
Actually, we _are_ hiding our source code.
We use various utilities for converting Perl or Python to 
double-clickable windows executables.
Ruby has this ability as well with the Exerb (though it is not quite 
as 'hidden' as the Perl or Python examples).

There are a variety of ways of 'hiding' code. One of the projects 
we're currently designing consists of a sealed box delivered to the 
user, a sort of 'payment appliance' if you will. The end user not 
only has no access to the code on the machine, they have no need for 
access. However, under the GPL, I would be legally bound to 
distribute source code for the program on that machine.

>You should also consider contacting the module owners.  They might grant you a
>special license.
Yes, that's always a possibility. However, I was also addressing the 
'how to make Ruby popular issue.' Please note that we're talking 
about a pretty fundamental module here -- basic database interfacing.
If I have a choice of working in an environment where the licenses 
promote commercial use or working in an environment where I need to 
check and perhaps get permission for special licenses, I'm going to 
take the path of least resistance.

Thanks again for your comments.
--Ray

--