Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5835
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: ilia@prohost.org
To: "Sara Golemon" <pollita@php.net>,
 <internals@lists.php.net>
Date: Sun, 30 Nov 2003 14:05:18 -0500
User-Agent: KMail/1.5.4
References: <200311300918.14257.magnus@php.net> <04b001c3b740$d8793d40$8802a8c0@obsidian> <002901c3b768$63adc440$0a00000a@alphaweb.net>
In-Reply-To: <002901c3b768$63adc440$0a00000a@alphaweb.net>
Organization: Prohost.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200311301405.18177.ilia@prohost.org>
Subject: Re: [PHP-DEV] Move old (or non-mainstream) extensions to PECL before beta 3
From: ilia@prohost.org (Ilia Alshanetsky)

On November 30, 2003 12:35 pm, Sara Golemon wrote:
> Perhaps I'm confused.....
>
> I had the impression that the point of moving obsolesced extensions to PECL
> was so that they WOULDN'T be included in the main source tarball.  Then,
> should user X out there need ext/foo they can do a:  pear install foo.
>
> If >that's< the case, then there need be no "pic up golden extensions at
> bundle time" script.  The creation of a tarball is just what it already is.

I guess I am confused as well, because I was under the same impression. 
My reasoning for removing obsolete extensions was to prevent dead (often 
poorly working code) from making it to the default distribution, which result 
in all kinds of problems.

> Are there any PECL extensions other than SQLite which are bundled at
> package time?

bz2 (in php5).

Ilia