Hi Lotte, MySQL's dual License policu is very simple. If you use the GPL license than you have to show the source code (modified or not), and include the Copyright info when passing the code on. If you dont want to do this (or in other words if you want to keep your modifications hidden) than you need a commercial license. So if you use mysql within your commercial product and sell it as a package and want to hide how/if you modified or improved the mysql source code than you will need the commercial license. Does that make sense ? Best regards Nils Valentin Tokyo / Japan > Hello, > > My understanding of the GPL license is that if you link your own software > with GPL-licensed software, then the GPL forces you to release the whole > thing under GPL. I am a bit confused that MySQL seems to require that even > stand-alone applications are released as open source. > > Does MySQL have a more strict interpretation of the GPL? Or is the license > on the MySQL GPL + more terms? Or? > > BR Lotte > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
