Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37670 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60899 invoked from network); 16 May 2008 00:05:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 May 2008 00:05:34 -0000 Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 38.99.98.18 beast.bluga.net Linux 2.6 Received: from [38.99.98.18] ([38.99.98.18:42294] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/F1-47746-DCFCC284 for ; Thu, 15 May 2008 20:05:33 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 9D149C0F849 for ; Thu, 15 May 2008 17:05:34 -0700 (MST) Received: from [192.168.0.106] (CPE-76-84-4-101.neb.res.rr.com [76.84.4.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 63A5FC0F844 for ; Thu, 15 May 2008 17:05:34 -0700 (MST) Message-ID: <482CCFCF.7080202@chiaraquartet.net> Date: Thu, 15 May 2008 19:05:35 -0500 User-Agent: Thunderbird 2.0.0.14 (X11/20080502) MIME-Version: 1.0 To: internals Mailing List X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: phar enabled by default as of now From: greg@chiaraquartet.net (Gregory Beaver) Hi, I just committed to ext/phar's config.m4/w32 to make phar enabled by default as a shared extension. This is a better default setting than building phar in statically, as phar has optional dependencies on the zlib and bz2 extensions to enable compressed phar archives. If phar is built statically, then it would require both zlib and bz2 to be built statically in order to use them, something that is obviously not going to happen, as they have been around a while and nobody has even suggested it (to my knowledge). Having phar shared means one can easily plug in zlib/bz2 support without recompiling PHP. I'm open to further input/tweaks on this decision. If you have a better idea, go ahead and commit to phar's config.m4/w32, these files are very easy to change if needed. Greg