Newsgroups: php.internals,php.pecl.dev
Path: news.php.net
Xref: news.php.net php.internals:56348 php.pecl.dev:8870
Return-Path: <philip@roshambo.org>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 43664 invoked from network); 16 Nov 2011 14:00:16 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Nov 2011 14:00:16 -0000
Authentication-Results: pb1.pair.com smtp.mail=philip@roshambo.org; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=philip@roshambo.org; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.210.170 cause and error)
X-PHP-List-Original-Sender: philip@roshambo.org
X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com  
Received: from [209.85.210.170] ([209.85.210.170:41630] helo=mail-iy0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id DE/66-11951-FE1C3CE4 for <pecl-dev@lists.php.net>; Wed, 16 Nov 2011 09:00:16 -0500
Received: by iakc1 with SMTP id c1so668622iak.29
        for <multiple recipients>; Wed, 16 Nov 2011 06:00:13 -0800 (PST)
Received: by 10.42.176.130 with SMTP id be2mr7874481icb.11.1321452012757;
        Wed, 16 Nov 2011 06:00:12 -0800 (PST)
Received: from [192.168.2.100] (c-98-246-13-68.hsd1.or.comcast.net. [98.246.13.68])
        by mx.google.com with ESMTPS id p16sm44768535ibk.6.2011.11.16.06.00.10
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 16 Nov 2011 06:00:11 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
In-Reply-To: <1321450474.29236.11.camel@guybrush>
Date: Wed, 16 Nov 2011 06:00:09 -0800
Cc: Ferenc Kovacs <tyra3l@gmail.com>,
 Felipe Pena <felipensp@gmail.com>,
 PHP Internals <internals@lists.php.net>,
 PECL Announce <pecl-dev@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <8587F05B-1916-419E-AA95-D239EC77CAD3@roshambo.org>
References: <CAH-PCH5odG590A3S9pa7af-VFaMKdg25nOnY7AyzwmqRfKLttQ@mail.gmail.com> <CA+5g0SJcMpMeEMiXUTo_H=bkUz76NigUE4tiKpwHj3vTffyzOQ@mail.gmail.com> <CAH-PCH5w3Nwe5nK+wzJowfdJrxiJK3MYitp4E+Ki9fNzqXdVng@mail.gmail.com> <1321450474.29236.11.camel@guybrush>
To: =?iso-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [PHP-DEV] pecl sqlite
From: philip@roshambo.org (Philip Olson)


On Nov 16, 2011, at 5:34 AM, Johannes Schl=FCter wrote:

> On Wed, 2011-11-16 at 13:35 +0100, Ferenc Kovacs wrote:
>> On Wed, Nov 16, 2011 at 12:53 PM, Felipe Pena <felipensp@gmail.com> =
wrote:
>>=20
>>> 2011/11/16 Ferenc Kovacs <tyra3l@gmail.com>:
>>>> Hi.
>>>>=20
>>>> We moved the sqlite ext from core to pecl with 5.4, but the
>>>> http://pecl.php.net/package/sqlite still advertises using =
ext/sqlite
>>>> instead.
>>>> Is that intentional?
>>>> The problem is, that for 5.3, the prefered way to use the sqlite =
ext is
>>> to
>>>> use the one bundled in core, however for 5.4 and trunk, you can =
only
>>>> install it from pecl.
>>>> Maybe we could supersed it with ext/sqlite3? As it is in the core =
since
>>>> 5.3, so all supported branches has it..
>>>=20
>>> It's not intentional, the text weren't updated.
>=20
> 5.4 is not yet released so PHP core is still the primary source for =
that
> extension ;-)
>=20
>> you mean the pecl package description?
>> I can change it, but where should it point to? sqlite3? or simply
>> unmaintained?
>=20
> I would go for unmaintained. SQLite2 isn't maintained upstream for a =
few
> years. People can get the code if they have need to migrate or such, =
but
> other than that ... there's no good and simple migration path to
> something else. SQLite3 uses different APIs, different storage format
> and has a slightly different SQL standard interpretation.

We need to make pecl/sqlite work with 5.4, as currently it does not. I=20=

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=20
pdo_sqlite2 to work with the shared PECL variant, IIRC. Then, make a=20
release.

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.

Johannes probably assumed I adjusted/committed the patch, and made a
pecl/sqlite release, but he forgot that I forgot to do this, and I have
since lost said patch and progress and most memories. Sorry :]

Regards,
Philip