ruben wrote:
I know the FAQ, and here's something from it:
"Combining two modules means connecting them together so that they form a single larger program. If either part is covered by the GPL, the whole combination must also be released under the GPL--if you can't, or won't, do that, you may not combine them."
This is why I'm against GPL. I can live with beeing forced to release the source code if I modify a GPL program. But I see no reason why I should GPL my entire product just because it uses a couple of functions from another GPL program.
Obviously those "couple of functions" must have some value if you'd rather not code it yourself. If you don't want to code it yourself, you're going to have to agree to somebody's licensing. It's either pay for propriatary code, agree to the GPL or hope that it shows up under a BSD license or public domain.
I apologize for the use of that word. I meant that GPL acts like a virus: if you touch a GPL program, your product becomes GPL as well.
Ah, "The Virus". A sound bite made press-worthy by Microsoft.
Here's a nice little page that explains why the GPL is not viral.