At 7:45 PM +0000 11/9/01, Carl Troein wrote:
>Shankar Unni writes:
>> What are the rules about "bundling" now? If we distribute a (standalone)
>> copy of MySQL with our product, does that expose our product to the GPL? Or
>> is it just like distributing a copy of Emacs with your OS? (I.e. as long as
>> you make the source available, it doesn't automatically GPL the rest of
>> your OS?)
>> What if the product is designed to work with many databases, but we want to
>> distribute MySQL only as a "default database" (i.e. it doesn't depend on
>> MySQL for its functionality - it's merely a convenience)? Does that change
>> the GPL liability on our product?
>> Who can answer these questions?
>I believe the GPL FAQ tries to address these questions:
>Specifically, this may be of interest to you:
>"By contrast, pipes, sockets and command-line arguments are
>communication mechanisms normally used between two separate
>programs. So when they are used for communication, the
>modules normally are separate programs."
Compare that with this section of the manual:
When you distribute a non-GPL application that ONLY works with the MySQL
server and ships it with MySQL. This type of solution is actually
considered to be linking even if it's done over a network.
I believe that bit about "even if it's done over the network" was
added sometime around last December. I'm not quite sure what to make
of it, particularly in light of the paragraph from the GPL FAQ.
> Carl Troein - CÌrdan / Istari-PixelMagic - UIN 16353280
> carl@stripped | http://pixelmagic.dyndns.org/~cirdan/
> Amiga user since '89, and damned proud of it too.