Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29307
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.233 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=RHFhAvMB1BhUiLFsHlkjVcifWU5pjG2FsZpuLNh8frICoxrV3GTgYCv/8m4ff0v0LIl1Vp33cpAxLv8HrhihU/h0e1P/qhP0uuzv3GSDVrW8Cu+LSbSkP09DhVLZJe5Rqq3BFLV8xFMWpnYWRV3BEL5Y+jKyV+wKi8HtjPCXDLE=
Message-ID: <fe05d1540705080113u2f675932i16de5ac6f997406f@mail.gmail.com>
Date: Tue, 8 May 2007 10:13:15 +0200
To: "Derick Rethans" <derick@php.net>
Cc: "Stanislav Malyshev" <stas@zend.com>, "Marcus Boerger" <helly@php.net>, 
	internals@lists.php.net
In-Reply-To: <alpine.DEB.0.98.0705080822260.27587@kossu.ez.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <139872287.20070504170744@marcus-boerger.de>
	 <1348470081.20070504221609@marcus-boerger.de>
	 <463EB3FD.4020009@zend.com>
	 <1062653277.20070507092725@marcus-boerger.de>
	 <463ED871.8080606@zend.com> <463F1B3A.3070703@pooteeweet.org>
	 <463F74EA.7030704@zend.com>
	 <1377895609.20070507211530@marcus-boerger.de>
	 <463F8909.6000709@zend.com>
	 <alpine.DEB.0.98.0705080822260.27587@kossu.ez.no>
Subject: Re: [PHP-DEV] [RFC] Starting 5.3
From: pierre.php@gmail.com (Pierre)

On 5/8/07, Derick Rethans <derick@php.net> wrote:
> On Mon, 7 May 2007, Stanislav Malyshev wrote:
>
> > > We will need it:
> > > - by the time of PHP 6
> >
> > I think this problem should be fixed not by killing PEAR and converting it to
> > PHP extensions but by fixing PHP 6 and enabling PEAR to work.
>
> Let me agree with Greg here. We can not go back to the PHP 4.x way of
> bundling PEAR. It's a PITA for both the PEAR people and the RM. PHP 5
> uses the phar, which works brilliantly. So the fix here is to make
> something *like* phar work with PHP 6 as well. If it was to be based on
> streams (which I think it can only be), then we *need* some way of
> marking this new user stream as being local in order for require and
> include to work on those. Making a hack in PHP to allow "phar://"
> streams to work is a bad idea, a C-extension can easily work here.

The point is to make local URL wrappers working, not only phar://.
Stanislav and Tony have a point, writing a custom extension to fix a
problem that we introduced is a bad idea and does not solve the
problem for anyone else but phar. If phar will be bundled or not does
not matter, this problem has to be solved anyway.

--Pierre