On Fri, 2009-07-17 at 16:09 +0800, Jens Jacobsen wrote:
> Just to clear a few tings up:
> 
> 5. DbLinq is such an application that is designed to load the GPL
> licensed Ingres and MySQL data providers and therefore in its current
> form cannot be distributed outside of the GPL.

Again, DbLinq is no more "designed" to load the GPL licensed MySQL
provider as .NET *itself* is.  DbLinq uses ONLY the standard ADO.NET
interfaces, period.

The only reason DbLinq even has the MySQL provider in svn is to
facilitate unit testing under MySQL.  They are not needed unless you're
actually using them (and the only ones using them are people running
DbLinq's unit tests under MySQL....which is no one, at this point).

The only thing that is really questionable is DbLinq.MySql.dll, which
(again) doesn't directly reference MySql.Data.dll.  ALL it does is
*generate* SQL in the MySQL dialect, e.g. use '?' for named parameters,
etc.  However, MySQL is not the only provider that accepts this dialect;
Mono has an MIT/X11 licensed ByteFX.Data ADO.NET provider which uses the
MySQL SQL dialect.  So I don't think you can convincingly argue that
generating SQL for the MySQL SQL dialect counts as "designed to use the
GPL licensed provider."

DbLinq, as currently designed, cannot add any additional GPL violations
over what System.Data already does.  Trying to argue otherwise is akin
to arguing that all uses of System.Data require GPL licensing (see other
email for more details).

(And I have never heard anyone before argue that because a GPL'd library
implements an existing 3rd party interface/protocol, all users of that
interface/protocol must also be GPL licensed.  It's crazy talk.)

 - Jon



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to