Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29193
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <463B8B36.5010906@zend.com>
Date: Fri, 04 May 2007 22:36:22 +0300
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Edin Kadribasic <edink@php.net>
CC:  internals@lists.php.net
References: <139872287.20070504170744@marcus-boerger.de> <9DC00D11-00A5-40DB-A397-8454C48FA448@prohost.org> <1525138013.20070504193205@marcus-boerger.de> <463B70A1.4010505@zend.com> <463B7232.7000205@php.net>
In-Reply-To: <463B7232.7000205@php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Starting 5.3
From: stas@zend.com (Stanislav Malyshev)

> obsolete set of tools (autoconf-2.13, etc.). Having Phar in the main
> distro will open up a whole new way to distribute PHP applications which
> would be a great advantage. The current system of distributing a bunch
> of PHP files has some shortcomings.

I'm personally not sure phar is that great way of distributing apps - 
it's yet another format not supported by standard tools and I don't 
really see much of an advantage to using it versus just making a package 
with any of the existing package formats and I see a number of 
disadvantages - non-standard format, hard to work with packed scripts 
with available filesystem tools, etc. But that's my opinion and I fully 
expect some people to hold exactly the opposite opinion. The question is 
however is phar so important that everybody needs it in the main source?
-- 
Stanislav Malyshev, Zend Products Engineer
stas@zend.com  http://www.zend.com/