Re: Re: PHP 5.0.0 Beta 1

The real issue is that the licensing for the MySQL libs has changes from LGPL to GPL. AFAICT that only affects MySQL 4.1 (which has a different API than previous version for what I can tell). That change will affect *any* language that links against those libraries, in particular if their license is not similar to the GPL (which *forces* the application using GPL libraries to be itself GPL). The PHP license is more BSD-like, thus allowing more freedom for anyone to use it, be it commercial or non-commercial, and does not impose a licensing term the way the GPL does. Thus the quandary. Unless you are someone who is not writing commercial applications, or do not mind releasing the code of your commercial application under the GPL, then that will pose a big problem for your code and your possibility to charge for it. MySQL is popular mainly because of its use as a web backend with PHP, but their decision of restricting (in a way) the use of their libraries may cause a re-evaluation for those planning on migrating to 4.1 (I know I am not going to, but rather move to PostgreSQL) Just my 0.02, and my (possible erroneous) personal understanding of the impasse as I am not a lawyer. Caveat: As I developer scientific web applications that are federally funded, this licensing change might not affect my current development/deployment. Just trying to put myself in the shoes of someone developing commercial applications. --- Stan Lemon <insyder@myrealbox.com> wrote: > Could be. All I'm saying is I have a feeling that's the part of the > license they are having a conflict with. > > Regardless... This brings a *serious* issue up for PHP, especially > since mySQL is so common amongst open source developers. Unless there > is some change it makes me hesitant to PHP5. > > - Stan > > Eric "e-dawg" Johnston wrote: > > >But PHP is Open Source. > > > >Might it be due to Zend? > > > >On Sun, 2003-06-29 at 18:56, Stan Lemon wrote: > > > > > >>I am assuming the following: > >> > >> > >> 3. Commercial use for everyone else > >> > >>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. > >> > >>Robert Cummings wrote: > >> > >> > >> > >>>I read the licensing information in the above link, but I'm curious what > >>>exactly in it necessitated the need to unbundle MySQL? Anyone have a > >>>quick answer? > >>> > >>>Cheers, > >>>Rob. > >>> > >>> > >>> > >>> > >> > >> > > > > > > > > > > > > > > -- > PEAR General Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > ===== -- Jesus M. Castagnetto (jcastagnetto@yahoo.com) Research: http://metallo.scripps.edu/ Personal: http://www.castagnetto.org/ __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com