hi Rasmus, On Tue, Nov 13, 2012 at 1:29 AM, Rasmus Lerdorf <ras...@lerdorf.com> wrote: > On 11/12/2012 07:24 AM, Leigh wrote: >> Hi, >> >>> We put ext/mysql in a (security) bug fix maintenance mode only >>> years ago. Too many ignore those attempts to get rid of ext/mysql. >> >> Maybe it's time to put it into full non-maintenance mode then? >> >> I believe MySQL is one of the on-by-default extensions when you >> compile PHP blindly (as I'm sure many do), why not make it require >> enabling specifically during build configuration, along with an >> end-of-script message that states the extension is no longer >> maintained (not even security fixes). > > That is simply not true. If you download PHP and do ./configure && make > install you do not get MySQL support. You have to explicitly specify > that you want it. > > What is true is that most people no longer build PHP at all. They just > end up with whatever their provider has installed or with whatever > packages they end up installing when they install the PHP app they want > to use. Both Wordpress and Drupal depends on php-mysql on Ubuntu, for > example. > > It would be good if we could get the majority of the major PHP apps to > commit to supporting mysqli along the same timeframe as marking this > deprecated.
Here is the take of one of the WP core dev: My take on the RFC: Toss E_DEPRECATED in already. In our case, developers will see them, be intrigued enough to contribute. and I gather we'd have it shipped built-in in Q2 2013. refs from a twitter conversation: https://twitter.com/nacin/status/268273606386126849 https://twitter.com/nacin/status/268273185307389952 Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
