Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:56370 php.pecl.dev:8878 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54776 invoked from network); 17 Nov 2011 21:00:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Nov 2011 21:00:14 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:58588] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 48/64-30628-6D575CE4 for ; Thu, 17 Nov 2011 16:00:12 -0500 Received: from [192.168.2.230] (ppp-93-104-126-236.dynamic.mnet-online.de [93.104.126.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 693C879A1C; Thu, 17 Nov 2011 22:00:00 +0100 (CET) To: Pierre Joye Cc: Philip Olson , Ferenc Kovacs , Felipe Pena , PHP Internals , PECL Announce In-Reply-To: References: <1321450474.29236.11.camel@guybrush> <8587F05B-1916-419E-AA95-D239EC77CAD3@roshambo.org> Content-Type: text/plain; charset="UTF-8" Date: Thu, 17 Nov 2011 21:59:58 +0100 Message-ID: <1321563598.29236.113.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] pecl sqlite From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Just to make one thing clear: To the best of my knowledge the module works with 5.4 and trunk (it's three months since I tested, but I'm not aware of a recent big API break) only defect is that the PDO sqlite2 driver won't be there and can't be enabled in an easy way. The patch I sent yesterday fixes that in one way. The mail mentioned another way. Whoever wants to release the extension can go for it easily. Aside from this specific case it is worth to discuss the role of PECL and Siberia for the future. This should happen in a dedicated thread with some proposal for a strategy and goal. johannes On Thu, 2011-11-17 at 14:08 +0100, Pierre Joye wrote: > hi, > > 2011/11/16 Philip Olson : > > > We need to make pecl/sqlite work with 5.4, as currently it does not. > > Why? We moved it out because it is not maintained anymore. As I agree > that the concept of "move to pecl" for dead extensions is a bad idea, > inciting users to continue to use with 5.4 instead of migrate their > code to sqlite3 is not a good thing. > > > I forget the details (and the related patch) but did work on one with > > Johannes many months ago. The last step (which failed) was to get > > pdo_sqlite2 to work with the shared PECL variant, IIRC. Then, make a > > release. > > It can be applied to svn. I suppose we should add a note as well in > the documentation about this move. > > > Moving something to PECL should require that the PECL extension work with > > the distribution that it was [re]moved from. Otherwise, it was not moved. > > I disagree, it should work with the distro where it was still present. > If we stop to support something with a given release, there is no > point to give the wrong message to our users. > > However, if someone feels like it is worth maintaining this dead > library binding and keep alive for 5.4+, he can indeed go ahead, but > unless we have such a person, I don't think we should release it or do > anything else for this extension and 5.4. > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org >