Hi, DbLinq uses databases drivers (mostly) via the standard interfaces and not directly (IDbConnection and friends), so this is to be considered as direct calls. In fact, DbLinq does not make special case for software, but only for language specificities. If writing specific SQL for MySQL and Ingres implies switching to GPL, then a lot of other software is in trouble, including big companies. So for the moment, nothing to be worried about :) And if one day, MySQL or Ingres people explicitly ask for being removed from DbLinq support, again then fine, but it's probably never going to happen.
Pascal. On Thu, Jul 16, 2009 at 12:06, Jens Jacobsen <[email protected]>wrote: > > From the previous discussion: > > >> Maybe I've got it all backwards, but how can DbLinq be licensed under > >> MIT when the MySQL .Net connector (MySql.Data.dll) that ships with > >> DbLinq is licensed under GPL? > >> > >> Because DbLinq does not distribute any database vendor. > > I'm afraid this is wrong. > > Distribution is not a requirement but referencing is. You cannot just > wrap a GPL library in BSD code and then "pretend" it is no longer GPL > unless you have the right to do so. > > The following is taken from the GPL FAQ: > > <quote> > Can I release a non-free (i.e. anything not GPL) program that's > designed to load a GPL-covered plug-in? > > It depends on how the program invokes its plug-ins. For instance, > if the program uses only simple fork and exec to invoke and > communicate with plug-ins, then the plug-ins are separate programs, so > the license of the plug-in makes no requirements about the main > program. > > If the program dynamically links plug-ins, and they make function > calls to each other and share data structures, we believe they form a > single program, which must be treated as an extension of both the main > program and the plug-ins. In order to use the GPL-covered plug-ins, > the main program must be released under the GPL or a GPL-compatible > free software license, and that the terms of the GPL must be followed > when the main program is distributed for use with these plug-ins. > > If the program dynamically links plug-ins, but the communication > between them is limited to invoking the ‘main’ function of the plug-in > with some options and waiting for it to return, that is a borderline > case. > > Using shared memory to communicate with complex data structures is > pretty much equivalent to dynamic linking. > </quote> > > Since DbLinq is designed to load Ingres and MySQL data providers and > interact with them, DbLinq is a GPL program and you have the choice to > either: > > 1. Change the license to GPL > 2. Remove MySQL and Ingres from the project. (This is the best > solution in my opinion). > > Regards > Jens > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
