Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29267 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37076 invoked by uid 1010); 7 May 2007 16:30:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 37060 invoked from network); 7 May 2007 16:30:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2007 16:30:04 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.139 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.139 c2bthomr07.btconnect.com Received: from [213.123.20.139] ([213.123.20.139:29632] helo=c2bthomr07.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 08/3A-56106-8045F364 for ; Mon, 07 May 2007 12:30:02 -0400 Received: from [127.0.0.1] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2bthomr07.btconnect.com with ESMTP id AAR77037 (AUTH lsces); Mon, 7 May 2007 17:29:57 +0100 (BST) Message-ID: <463F53B2.2030009@lsces.co.uk> Date: Mon, 07 May 2007 17:28:34 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1 MIME-Version: 1.0 To: PHP internals References: <139872287.20070504170744@marcus-boerger.de> <736AED54-1272-4924-A07D-3166A1742A2F@prohost.org> <698DE66518E7CA45812BD18E807866CE2FEF72@us-ex1.zend.net> <463EDD0B.7080300@lsces.co.uk> <463F3724.1070703@chiaraquartet.net> In-Reply-To: <463F3724.1070703@chiaraquartet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Starting 5.3 From: lester@lsces.co.uk (Lester Caine) Gregory Beaver wrote: > Phar is not yet perfect, but is also not NEARLY as complex as PDO. > There is no comparison. The 'comparison' was in the way these packages get added without proper investigation ;) Someone decides that THIS is how it will be done, and that is what happens :( and we have to live with the consequences. How would I use 'phar' with the four thousand files that make up bitweaver? I have had a quick look, but I don't yet see how I handle all the installation and management options for installing and updating packages that bitweaver has been designed to support. ADOdb and smarty provide the core libraries, and the liberty shell is built on those. Only those packages that are needed are download to the target system. I suspect we would have to build phar files for each package, but currently styles and themes can easily be managed via a few file changes, something that phar would seem to make a lot more difficult. Private tweaks to the libraries provide performance and operational improvements that would not be possible if ADOdb or smarty were supplied 'packed'. But without example phar libraries to look at and pull apart proper investigation is difficult - as people have already said. -- Lester Caine - G8HFL ----------------------------- Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact L.S.Caine Electronic Services - http://home.lsces.co.uk MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/ Firebird Foundation Inc. - http://www.firebirdsql.org/index.php