On Wed, Aug 11, 2004 at 05:43:16PM +0200, Leonardo Francalanci <[EMAIL PROTECTED]> wrote: > > If you develop a product, say, some kind of online shopping > > system that you > > distribute on a CD which installs Linux, Apache, MysQL, PHP and > > your App and > > distribute that, then you probably should be paying for a license. This is > > because instead of you handing over full code (and it's rights) to the > > client as their property, you are placing licensing limitations on it. > > Ok, but if I say to a client (that has his own web server) "you will > need to install Mysql on your server to run the site I'm writing for > you", will he > need a license?
Look at it this way: No matter what, *everyone* using MySQL requires a license. Here's the question you need to ask: Which of the two possible licenses can I use without contravening the terms? Obviously, you'd rather not pay, so you want to look at the GPL first. To do that, you and/or your company's lawyer need to read the terms of the GPL and apply them to the way you wish to use the software. If you reach a term which you are unable to comply with, then you can't use the GPL, and need a commercial license. But you're entering into a legal agreement with MySQL AB, so you need to read every term in the license and determine, with legal assistance if you need it, whether or not you can do what you want to do under the license's terms. The mailing list is probably a bad place to turn for legal advice (which, incidentally, I am not giving you right now :-). -Rich -- Rich Lafferty --------------+----------------------------------------------- Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus! http://www.lafferty.ca/ | http://zapatopi.net/treeoctopus.html [EMAIL PROTECTED] -----------+----------------------------------------------- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
