b) If you include one of the MySQL drivers in your non Open Source application (so that your application can run with MySQL), you need a commercial licence for the driver(s) in question. The MySQL drivers currently include an ODBC driver, a JDBC driver and the C language library. Please note that even if you ship a free demo version of your own application, the above rules apply."
As long as we are talking about pure GPL this doesn't matter.
As long as you don't link your application against the GPL'ed code they can't touch you, the trick is that if you use a standard interface like JDBC or ODBC then your code doesn't link against the GPL'ed code, the actual act of linking your application to the GPL'ed code happens when the user configures your application to use a certain driver, your application doesn't have any control over that so you are in the clear.
The user is bound by the GPL to not distribute the resulting system, but that doesn't matter because he wasn't going to do that anyway.
Unless the license is something other than GPL you should be in the clear, I think, but IANAL.
Someone should ask RMS about this:)
-- Regards Flemming Frandsen - http://dion.swamp.dk PartyTicket.Net co founder & Yet Another Perl Hacker
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
