Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2507
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-Type: text/plain;
  charset="iso-8859-1"
To: Sterling Hughes <sterling@bumblebury.com>,
 internals@lists.php.net
Date: Sat, 21 Jun 2003 22:17:05 +0200
References: <1056210210.26964.4.camel@hasele>
In-Reply-To: <1056210210.26964.4.camel@hasele>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <19ToqA-162mKu0@fmrl11.sul.t-online.com>
Subject: Re: [PHP-DEV] removing bundled libmysql
From: georg@php.net (Georg Richter)

Hi all,

as maintainer of ext/mysql and ext/mysqli I'm standing between php and mysql, 
and I spent a lot of time on both extensions, so don't ask me :)

Currently bundled libmysql prevents users to violate license. If you need an 
external lib, you normally download latest stable, which is 4.0.x and is GPL.
According to the MySQL license, you need a commercial license when using PHP 
4 with MySQL 4.x, cause PHP license isn't a) OSI approved and b) GPL 
compatible.

We have the same problem with ext/mysqli which isn't compatible to GPL, and 
will be removed therefore from PHP 5 beta.

The combination with MySQL was one of the reasons that PHP growed up to one 
of the best and most used scripting languages. PHP was one reason, that MySQL 
became one the most popular OpenSource databases. So I ask you, is it really 
necessary, that we try to force a decision. 

Zak is already working on license problems, incompatibility and possible 
solutions. Wouldn't it be better to give him and MySQL AB a little bit more 
time?

Just my 2 cents

Georg