Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34979
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.150 cause and error)
Message-ID: <03c801c861e5$6bc35e70$c6fc1f3e@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Pierre Joye" <pierre.php@gmail.com>,
	"Stanislav Malyshev" <stas@zend.com>
Cc: "Gregory Beaver" <greg@chiaraquartet.net>,
	"internals Mailing List" <internals@lists.php.net>
References: <479E1152.50301@chiaraquartet.net> <479E2455.4040508@zend.com> <fe05d1540801281124n18055993jdc5ad8a832b25f88@mail.gmail.com>
Date: Mon, 28 Jan 2008 19:38:54 -0000
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] re-proposal of pecl/phar for inclusion in core
From: steph@zend.com ("Steph Fox")

Hi Pierre,

> Exactly and I'm rather surprised to see this post given the recent
> efforts to export the Zip symbols to allow any extension to share the
> zip features.

I think until the zip features were shared the library's limitations hadn't 
been too obvious.

> Most of the discussions have been public on pecl-dev.
> There is some private discussions about our respective plans, even
> today.

Not that I'm aware of...

I can say that the goals and APIs are different, there is a
> need for both extensions (zip will never provide what phar does for
> the application archive and pahr will never go as far as zip for the
> zip format support), that's my understanding of the current situation.

That's my understanding too.

> However, my point remains intact, I'm not in favour of having phar
> included. Unless there is an improved cooperation with the community
> (in large) to create this application-archive format.

What exactly would we need to do to improve cooperation?

 It would really
> rock to have a standard format designed, approved and adopted by all
> PHP developers and projects. At this point we can bundle it or it may
> be a chicken-egg problem :)

Well, that's why the aim is to get it bundled now. Because using the Phar 
extension you can now optionally write phars that can be opened by: tar (+ 
bzip2/zlib), zip (including Windows Explorer), or plain PHP, either CLI or 
through a browser, using the default stub; it's about as flexible as anyone 
could want it to be. There's still also the option to write phars that 
require ext/phar enabled before they can be read, which personally I think 
is a bad idea but Marcus wanted it that way.

- Steph


>
> Cheers,
> -- 
> Pierre
> http://blog.thepimp.net | http://www.libgd.org
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>