No subject

If you distribute a proprietary application in any way, and you are not licensing and distributing your source code under GPL, you need to purchase a commercial license of MySQL


Is this really the case?  If so, how does ByteFX get away with being called lgpl given that MySQL is using the GPL as the basis for their argument.  What about Mono's MySql client?

Chris



> 
> From: "Luis Fernandez" <luifer at onetel.com>
> Date: 2004/09/16 Thu PM 03:08:22 EDT
> To: <mono-devel-list at lists.ximian.com>
> Subject: RE: RE: [Mono-devel-list] ByteFX development
> 
> RE: RE: [Mono-devel-list] ByteFX developmentHi All,
> 
> Please, correct me if I'm wrong, but I believe that the licence of the MySql
> database only allows you to develop apps that are open source. If you are
> intending on selling/distributing a commercial product that uses MySql as
> the backend, then you are required you to purchase a comercial licence for
> MySql.
> 
> Because of this, the LGPL version of ByteFX is only of any use to open
> source projects. If you want to sell a comercial product, you need to
> purchase the licence, which I guess will also include their commercial
> version of the GPL library that MySql provides.
> 
> I think this might eliminate the need to develop the LGPL version if the
> main intent is that it can be use in commercial applications.
> 
> Hope I 'm wrong in my understandind of the MySql Licence but I think it's
> worth checking before doing the work...
> 
> Thanks for your great work mono developers :)
> 
> Regards,
> Luis
> 
> 
>   -----Original Message-----
>   From: mono-devel-list-admin at lists.ximian.com
> [mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of Belbin, Peter
>   Sent: 16 September 2004 19:11
>   To: 'cmorgan at alum.wpi.edu'; Belbin, Peter; 'Miguel de Icaza'
>   Cc: mono-devel-list at lists.ximian.com
>   Subject: RE: RE: [Mono-devel-list] ByteFX development
> 
> 
>   Yes, I agree, that is more of an issue if you are intending to sell a
> product based on GPL code.
> 
>   However, I would think that you could pay them a fee and obtain the same
> code under a different license
>   if the time came to actually making money out of it.
> 
> 
> 
> 
>   -----Original Message-----
>   From: Chris Morgan [mailto:chmorgan at charter.net]
>   Sent: Thursday, September 16, 2004 10:11 AM
>   To: Belbin, Peter; 'Miguel de Icaza'
>   Cc: mono-devel-list at lists.ximian.com
>   Subject: Re: RE: [Mono-devel-list] ByteFX development
> 
>   > If you have a look at the www.ByteFX.com and go to the data provider
>   > tab, you'll see there that Reggie is now part of MySQL and the ByteFX
>   > code is what he is developing for them.
>   >
>   > I don't see any reason why, given the work he's doing, you wouldn't
>   > want to stick with his code, since I understand he is making sure that
>   > it's mono compatible.
>   >
>   > Reggie has always been responsive to any issues that have arisen, and
>   > I would hope that he is just as responsive these days, even though
>   > he's probably got some other stuff to work on as well.
>   >
>   > Regards,
>   > Peter.
>   >
> 
>   The licensing of MySQL makes it less than appealing for commercial use.
> As I mentioned in my first email, the license has changed from lgpl to gpl
> meaning that any applications that use the MySQL connector become gpl'ed.
> Here is the link to the connector downloads page:
> 
>   http://dev.mysql.com/downloads/connector/net/1.0.html
> 
>   Here is the GNU description of whether you can link or not:
> 
>   http://www.gnu.org/licenses/gpl-faq.html#LinkingWithGPL
> 
>   Given this it seems very useful to maintain development of a lgpl MySQL
> client.
> 
>   Chris
> 
> 
> 
> 
> 
>   NOTICE: This electronic mail transmission may contain confidential
> information and is intended only for the person(s) named.  Any use, copying
> or disclosure by any other person is strictly prohibited. If you have
> received this transmission in error, please notify the sender via e-mail.
> 
> 
> 
> 
>