Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29237 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49775 invoked by uid 1010); 7 May 2007 07:27:21 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 49759 invoked from network); 7 May 2007 07:27:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2007 07:27:21 -0000 Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 85.214.94.56 cause and error) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Received: from [85.214.94.56] ([85.214.94.56:57748] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4A/4A-52548-9D4DE364 for ; Mon, 07 May 2007 03:27:21 -0400 Received: from baumbart.mbo (dslb-084-063-004-200.pools.arcor-ip.net [84.63.4.200]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id A3DFA1B3629; Mon, 7 May 2007 09:27:18 +0200 (CEST) Date: Mon, 7 May 2007 09:27:25 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1062653277.20070507092725@marcus-boerger.de> To: Stanislav Malyshev CC: Edin Kadribasic , internals@lists.php.net In-Reply-To: <463EB3FD.4020009@zend.com> 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> <463B8B36.5010906@zend.com> <1992195966.20070504214413@marcus-boerger.de> <463B9271.3040009@zend.com> <1348470081.20070504221609@marcus-boerger.de> <463EB3FD.4020009@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Starting 5.3 From: helly@php.net (Marcus Boerger) Hello Stanislav, Monday, May 7, 2007, 7:07:09 AM, you wrote: >> they most likely don't, it is designed for deployment and for running >> includes directly. > What do you mean "directly"? Do you mean this is designed for running > application only specifically crafted to run inside phar and would break > some or most of the existing applications not designed specifically for > it? Then even less reason to recommend it as a way to deploy real > applications. It means you can run a phar file. How is that so hard to understand. See the docs: http://php.net/phar >> pear install phar - or - pecl install phar - done >> oh wait the point is that pecl install doesn't work or is in 99% no option > And what is "pear install"? I don't have such command in my Windows by > default. Neither I have it on my Linux. I would have to install PEAR for > that, right? Even only to know what's inside. Well alot of people make use of our PEAR project. It comes with a bunch of nice sub projects. And even some external (as in non PHP) applications and projects make use of it. Providing a better internal infrastructure would be very nice here. >> slow? bigger? overhead? > Meaning, of no practical use nobody would package their real-world apps > this way. Then I guess it's not really an option? As said you can try stuff in a phar and then extract it. And lemme think, a war or jar or whatever crap doesn't make java faster either. But hey it would be a nice trick to turn PHP evenmore into Java so you should promote it. >> Interesting and not maintained for the most. Sometimes working on one or >> the other very specific php version only. And often even without >> documentation. > This is as I see for very specific applications too, and the manual says > there's no currently stable version of phar. Strange, pecl lists three stable versions since end of march: http://pecl.php.net/package/phar And phar has been stable since end of last year. We only decided to not mark it stable to be able to rename a few things. > My opinion I see > is that it is not right to recommend it as preferred way to > deploy PHP applications. I know there are many people that it suits > their needs - but those people as I understand have to keep in mind they > work for phar anyway, so they might as well install one more extension. Once again, that is in most cases no option at all. Best regards, Marcus