On Tuesday 04 Jan 2011, Shamit Verma wrote: > 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/
The exception is like the LGPL but is not actually exactly the LGPL. According to the LGPL, you can link an LGPL library into a proprietary product provided you either (a) do not change the library or (b) ship the source of the modified library along with the rest of your product. Note that the LGPL does not force you to expose the rest of the code of your product. The MySQL library code is GPL, but the exception permits you to link another non-GPL FOSS (Note: NOT proprietary) application with the library. If the exception weren't present, only GPL applications could link with the MySQL library. In other words, the LGPL lets you link proprietary code with the library, while the MySQL exception only lets you link other FOSS code with the library. The MySQL library remains under the GPL and you cannot link that with proprietary code. That's my reading of the exception, I'm open to correction if I've got it grossly wrong. Regards, -- Raj -- Raj Mathur [email protected] http://kandalaya.org/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F PsyTrance & Chill: http://schizoid.in/ || It is the mind that moves -- http://mm.glug-bom.org/mailman/listinfo/linuxers
