Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36871 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61914 invoked from network); 8 Apr 2008 14:12:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Apr 2008 14:12:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=gwang@litespeedtech.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=gwang@litespeedtech.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain litespeedtech.com designates 64.18.140.195 as permitted sender) X-PHP-List-Original-Sender: gwang@litespeedtech.com X-Host-Fingerprint: 64.18.140.195 mail.litespeedtech.com Received: from [64.18.140.195] ([64.18.140.195:44528] helo=mail.litespeedtech.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 26/8A-22202-16D7BF74 for ; Tue, 08 Apr 2008 10:12:50 -0400 Received: from ool-43515bdf.dyn.optonline.net ([67.81.91.223] helo=[192.168.0.154]) by mail.litespeedtech.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1JjEYz-0002UI-2q; Tue, 08 Apr 2008 10:12:46 -0400 Message-ID: <47FB7D58.6000505@litespeedtech.com> Date: Tue, 08 Apr 2008 10:12:40 -0400 User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= CC: internals@lists.php.net References: <47E80EB9.60900@litespeedtech.com> <47E81136.3040308@zend.com> <47E81315.4060601@lerdorf.com> <47E82351.6040004@litespeedtech.com> <47EAAD1C.2050100@litespeedtech.com> <1206574218.11056.24.camel@goldfinger> In-Reply-To: <1206574218.11056.24.camel@goldfinger> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -3.2 (---) X-Spam-Report: Spam detection software, running on the system "mail.litespeedtech.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see admin@litespeedtech.com for details. Content preview: Hi Johannes, > Well, the idea is that all PHP-specific code is licensed under the same > license terms. PCRE and GD are external libraries which live outside > PHP's context and which are simply bundled. That's why the clear > preference there is PHP License. > I have updated the license to have it dual-licensed under PHP and BSD licenses. [...] Content analysis details: (-3.2 points, 5.3 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.1 SPF_FAIL SPF: sender does not match SPF record (fail) [SPF failed: Please see http://spf.pobox.com/why.html?sender=gwang%40litespeedtech.com&ip=67.81.91.223&receiver=mail.litespeedtech.com] -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.1 AWL AWL: From: address is in the auto white-list Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP distribution? From: gwang@litespeedtech.com (George Wang) Hi Johannes, > Well, the idea is that all PHP-specific code is licensed under the same > license terms. PCRE and GD are external libraries which live outside > PHP's context and which are simply bundled. That's why the clear > preference there is PHP License. > I have updated the license to have it dual-licensed under PHP and BSD licenses. > Additionally it would nice to follow the PHP coding standards. Like > always having { } after an if statement. This helps PHP developers who > might (possibly) help fixing reported (simple) bugs or apply API > changes. > The code has been updated to follow the PHP coding standards in regard of using { }, if there is any other issue, please let me know, I will fix it ASAP. > Other than that we, again, have our problem about what's the best way to > "bundle" something from pecl. I guess the symlink on the CVS server is > the best option we currently have... > Either a symlink or moving the directory physically to where other SAPI code are should work. I can check in the code to a different location if need. Please let me know if anything I can help. :-) Thanks, George