Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66437 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68586 invoked from network); 3 Mar 2013 07:41:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Mar 2013 07:41:18 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.128.41 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.128.41 mail-qe0-f41.google.com Received: from [209.85.128.41] ([209.85.128.41:40716] helo=mail-qe0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/81-59723-D9EF2315 for ; Sun, 03 Mar 2013 02:41:18 -0500 Received: by mail-qe0-f41.google.com with SMTP id 6so3266894qeb.14 for ; Sat, 02 Mar 2013 23:41:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=VEpAgw5GmhbF1kzDBqBFTqUvCos65Q783y/vcpYp9TE=; b=pR79nmODfRFENb17+WGMErzY2kMAIjAzqLA8BLeAM+z6Z4d2UYxq0iJaSGHb8wnXv4 JeWtOjg0BSn/cDzWb5aaSiQjGyyg0HD9yhiMJG7ZohuPuV3Ekcg7yOGh+ps+OQ8Om3+G fwWdgjDbWEyIOJWLL+DIdKwDSOfjBdrHMehUoBIKz38Ok2syBQsL38M0XiPJw+ctKsdD kv+9BETXUeghbbSEIDJ6XgkLrPkJaEfYmQZsn3Yy8NGbG2zOoYgj0eOFl4+ZHwu/6biZ wgSG0c92PYq0LW+PHhol7TgNPKZl51F3AZWU2M3L+thwOXGfcfC8lS3pTSJuGgITKopr E/7w== X-Received: by 10.229.106.83 with SMTP id w19mr5733688qco.45.1362296474891; Sat, 02 Mar 2013 23:41:14 -0800 (PST) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id 8sm29799780qed.6.2013.03.02.23.41.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 02 Mar 2013 23:41:14 -0800 (PST) Message-ID: <5132FE98.5050201@lerdorf.com> Date: Sat, 02 Mar 2013 23:41:12 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Pierre Joye CC: Zeev Suraski , Laruence , PHP Developers Mailing List References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <8944597477930141639@unknownmsgid> <1a0793107537dceb9cc67c616294ce76@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlDdLu5eMsD7OQT0Lbs623WWbXz01RC7M5MU6loEOcLu2qHMfp2n55WgOoDnSv7GQWF9bz7 Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution From: rasmus@lerdorf.com (Rasmus Lerdorf) On 03/02/2013 11:25 PM, Pierre Joye wrote: > On Sun, Mar 3, 2013 at 8:21 AM, Zeev Suraski wrote: >>> How "Don't integrate Optimizer+ to PHP" can be remotely related to the >>> available of o+ via PECL? >> >> Actually it seems as if some of the original text got lost when I switched >> to the active vote, but it used to read 'Don't integrate Optimizer+ to >> PHP, release only in PECL'. My bad. > > > No offense and pls do not see what I will say here as an attempt to > block it, as I really want o+ in core. > > I think this RFC should be fixed (fix wording to represent the actual > actions, s,integration,bundling&cleanup,), votes options added to > cover what has been discussed. Add a roadmap as well for the further > steps that can/could/will be taken to make o+ even better while being > in core. > > The options should include PECL, either it is in core or not. So you > can get an idea about how many people wants < 5.5 support and releases > as well. The RFC is about integrating O+ into PHP which can by definition only happen in 5.5 and later. The essential questions being asked by the RFC are whether to delay 5.5 for it, no delay and wait until the next version, or don't integrate at all the last of which implies external-only distribution either through pecl or individual distros simply packaging it from Github. And your beef about integration vs. bundling is rather nit-picky. The first step towards integration is getting it in. How much integration is done will depend on what people come up with. I have a pull request in for at least one level of integration that will allow it to save a stat call by integrating more closely with the sapi layer to save that initial stat if the sapi layer can pull it from the server layer. That is more than mere bundling, but it should also be rather safe to do. What we do about earlier versions is a completely separate and mostly unrelated issue. There is no real reason not to support those via pecl, but that isn't what this RFC is about. And, like you say, there is nothing stopping you or anybody else from making a pointer to it from pecl. -Rasmus