On Aug 11, 2004, at 7:09, Leonardo Francalanci 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?
We always recommend that proprietary use of MySQL be done under our
for-pay license. This is a simple recommendation that helps us fund
development and is always correct.
However, if you are creating a work for a client who has hired you to
build something for them, then chances are quite good that MySQL can
legally be used under the GPL.
If you build a proprietary software product that is based on MySQL and
distribute this to customers, then you probably can't do so with the
GPL licensed version of MySQL and would need to purchase non-GPL
licenses for MySQL.
MySQL AB Community Advocate