28/05/2003 07:47:41, Flemming Frandsen <[EMAIL PROTECTED]> wrote: >Now the application developer didn't do this linking at all so he is in >the clear, the one doing the possibly violating linking is the user >himself and if he doesn't go around copying the resulting setup to >another site then everything is fine. > >The same thing goes for the JDBC client, the linking doesn't happen at >compile time and the user can tell the application to link to whatever >JDBC driver there is, so the application developer doesn't have anything >to do with that. > >So if the license is changed to straight GPL then noone needs to do >anything differently. >
Have a look at MySQL's licence page: http://www.mysql.com/products/licensing.html Quote: " a) If you include the MySQL server in your non Open Source application, you need a commercial licence for the MySQL server 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." Regards, Tarlika Elisabeth Schmitz ___________________________________________________________________________ Numerix Technology Limited www.NumerixTechnology.com _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
