Paul DuBois writes:
> 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. Interesting. As the GPL FAQ points out, the interpretation of the GPL in cases like this would ultimately have to be tested in court. I have a feeling that that paragraph on the MySQL site is enough to tip the scales. At least it's enough to make anyone who chooses to bundle MySQL with a non-GPL application aware of the possible license violation that this constitutes. The workaround would of course be to include support for one more RDBMS, or to just not ship with MySQL. Thanks for pointing this out to me. This information may be useful to me in the future, as although I'd love to release it under the GPL, the project I'm working on involves two more people, and they don't seem to be so easy to convince. Specifically, their concern is what potential buyers will think of aquiring something that might be available to their customers for free. My counter-argument would be that if someone wants to pay us to incorporate it into a proprietary product, some sort of value has to be added, and that is what people will pay for. //C -- Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280 [EMAIL PROTECTED] | http://pixelmagic.dyndns.org/~cirdan/ Amiga user since '89, and damned proud of it too. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
