2011/1/3 Raj Mathur (राज माथुर) raju@linux-delhi.org
People who make packages with libraries (or just libraries), like Qt used to be and MySQL is today, prefer the GPL for their libraries because then their product cannot be incorporated into a proprietary product. So if you are using, say, MySQL to develop your proprietary application you need to use the MySQL libraries for your app to interact with the database. Since the MySQL library is under the GPL, any code linked to it also must be under the GPL.
Agree with overall message of this email, just correcting a minor fact.
MySQL code is GPL, but MySQL Library code is LGPL.
That is specifically to address this situation. If you are creating a product:
1. If product uses MySQL engine in embedded mode, product MUST be GPL (or have license from Oracle for redistribution) 2. If product only uses client libraries, it need not be GPL. It can even be BSD licensed
Details : http://www.mysql.com/about/legal/licensing/foss-exception/
-Shamit