Please take a look at:
http://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL

It states:
«If a library is released under the GPL (not the LGPL), does that mean that any program which uses it has to be under the GPL?
Yes, because the program as it is actually run includes the library.»
So, I guess I was and I am right.

If I remember right, there is something called FLOSS (or very similar) in MySql license that allows you to release your application (the one linking to a MySql licensed library) under a license compatible to GPL *and* approved by that FLOSS. Not sure what that means but I assume that you can do a LGPL library that used .net connector, thus allowing other to link to your app with any other license, including closed-source.

There is a workaround that I was told to work well - to make sure your app works with other providers, like postgres, sqlserver, access, etc.... and load the provider dynamically, that is, as an addin (using a xml file and reflection....). Again, I'm not sure this works, but I believe so.

On 11/6/05, Alexandre Miguel Pedro Gomes <[EMAIL PROTECTED]> wrote:


---------- Forwarded message ----------
From: Jay Bennie < [EMAIL PROTECTED]>
Date: Nov 6, 2005 8:44 AM
Subject: Re: [Mono-list] Recommended MySQL Data Provider?
To: Alexandre Miguel Pedro Gomes <[EMAIL PROTECTED] >

Alexandre Miguel Pedro Gomes wrote:
> By using the official MySql .Net Connector you are making your
> application GPL, unless you buy a commercial license.
>
> Just a warning :)

no you are not! this is a common misinterpretation of GPL

if your application extends and modifies the Mysql .net connector then
that extention become GPL not the whole application

simpy using the GPL code does not make your application GPL.




--
Alexandre Gomes, Portugal



--
Alexandre Gomes, Portugal
_______________________________________________
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to