Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39900 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1915 invoked from network); 12 Aug 2008 21:51:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Aug 2008 21:51:30 -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 208.83.222.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 208.83.222.18 unknown Linux 2.6 Received: from [208.83.222.18] ([208.83.222.18:50395] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 83/2C-04075-0E502A84 for ; Tue, 12 Aug 2008 17:51:29 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 9DE1EC0D8B7; Tue, 12 Aug 2008 14:51:16 -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 07108C0D848; Tue, 12 Aug 2008 14:51:15 -0700 (MST) Message-ID: <48A205DA.9000101@chiaraquartet.net> Date: Tue, 12 Aug 2008 16:51:22 -0500 User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Antony Dovgal CC: php-dev References: <4892E15D.1080004@daylessday.org> <48A19D61.6080502@daylessday.org> In-Reply-To: <48A19D61.6080502@daylessday.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] enabling everything by default From: greg@chiaraquartet.net (Gregory Beaver) Antony Dovgal wrote: > On 01.08.2008 14:11, Antony Dovgal wrote: >> I can agree that disabling something that was already enabled in 5.2 >> might create some confusion, but why enable scarcely created >> extensions by default, especially if they are known to cause lost of >> obscure problems in the past (like Phar)? > > See http://bugs.php.net/bug.php?id=45613 for example. > Who would have thought that there are multithreaded web-servers, eh? > > I'm going to disable ext/phar before alpha2. > You've been warned. Hi, I've just returned home finally, and look forward to taking a look at issues. I even committed 2 new code coverage tests while on the road, in case you doubt my resolve to fix things up. Tony, please drop the posturing, it makes you look somewhat ridiculous :). I *explicitly* asked that the question of enabling phar by default be voted on prior to rc 1 when I enabled it, and again reminded about it a month later. Please see the links below to the emails in question. Let's not forget - disabling ext/phar by default involves changing a 1 to a 0 in config.m4, it's hardly difficult to do. I agree that it needs to happen prior to the final release cycle or not at all. Is alpha2 the new rc1? That makes no sense to me if so. Thanks, Greg From May 14, 2008: http://marc.info/?l=php-internals&m=121078127525090&w=2 From June 23, 2008: http://marc.info/?l=php-internals&m=121419199122615&w=2