Am 02.09.2011 21:24, schrieb Stas Malyshev:
Hi!
On 9/2/11 12:17 PM, Christopher Jones wrote:
I'm +1 for this. I think the decision& implementation needs to be done
before Beta or deferred to trunk.
Frankly, I'd be more comfortable with trunk. We have enough trouble with
unit tests etc. before the beta, and introducing profound change in
default without enough time for discussion and gathering feedback from
packagers, etc. doesn't look a smart thing to do.
Hmm, I do not understand the unit test argument. Non-portable tests
exist regardless of what the config.m4 default is.
We are talking about making mysqlnd as a compile default, if not
explicitly choosing libmysql to compile against. This is no attempt to
remove libmysql support. I somewhat assume most packagers do explicitly
set libmysql path already and do not rely on any magic, because they
don't use MySQL's default source layout. However, argument taken, let's
do some checks who (Debian, Ubuntu, OpenSuse, RH, ...) does not set
libmysql path during compile.
mysqlnd was introduced with PHP 5.3. IMHO, it has matured quite well.
Mysqlnd reduces the PHP projects dependency on anybody controlling the
library. This has been a major pain in the past. Think of builds made
against outdated versions of libmysql, think of waiting for new libmysql
releases, think of compilers not supported by libmysql, think of license
discussion, think of accepting code contributions and so forth.
From a user perspective mysqlnd removes the need to install libmyql
prior to building and a has a couple of neat features not available with
libmysql, for example, the plugins.
Ulf
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
