Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35235 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76925 invoked by uid 1010); 6 Feb 2008 10:30:45 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 76910 invoked from network); 6 Feb 2008 10:30:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Feb 2008 10:30:44 -0000 Authentication-Results: pb1.pair.com header.from=steph@zend.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=steph@zend.com; spf=permerror; sender-id=softfail Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.159 cause and error) X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 64.97.136.159 smtpout0159.sc1.he.tucows.com Solaris 8 (1) Received: from [64.97.136.159] ([64.97.136.159:37818] helo=n066.sc1.he.tucows.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A8/30-03555-35C89A74 for ; Wed, 06 Feb 2008 05:30:44 -0500 Received: from sc1-out05.emaildefenseservice.com (64.97.139.2) by n066.sc1.he.tucows.com (7.2.069.1) id 4769F9180057679E; Wed, 6 Feb 2008 10:29:59 +0000 X-SpamScore: 2 X-Spamcatcher-Summary: 2,0,0,c0f82b72f57eeba9,942ddd6a8e1e3a25,steph@zend.com,-,RULES_HIT:355:379:539:540:541:542:543:567:599:601:973:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1487:1515:1516:1518:1534:1541:1587:1593:1594:1711:1730:1747:1766:1792:2073:2075:2078:2393:2559:2562:2693:2736:2828:2894:3027:3354:3622:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:4250:4401:5007:6117:6119:6120:6261:7653,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache: 0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none X-Spamcatcher-Explanation: Received: from foxbox (62-31-252-198.cable.ubr07.shef.blueyonder.co.uk [62.31.252.198]) (Authenticated sender: steph.fox) by sc1-out05.emaildefenseservice.com (Postfix) with ESMTP; Wed, 6 Feb 2008 10:29:57 +0000 (UTC) Message-ID: <00a401c868ab$57ceb500$c6fc1f3e@foxbox> Reply-To: "Steph Fox" To: "Marco" Cc: "Derick Rethans" , "Marcus Boerger" , "internals" References: <01c801c865d8$2e837e90$c6fc1f3e@foxbox> <14581063.20080203002104@marcus-boerger.de> <005201c8660f$66a2b160$c6fc1f3e@foxbox> <00f501c86743$e5122320$c6fc1f3e@foxbox> <2fd662a00802060057r51bdbb6dqd0b6c65133424618@mail.gmail.com> <005101c868a2$aaf235d0$c6fc1f3e@foxbox> <2fd662a00802060212v245b9645q2449735c0d660667@mail.gmail.com> Date: Wed, 6 Feb 2008 10:30:47 -0000 Organization: Zend Technologies MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-DEV] Splitting the subject: the PECL/PHP relationship From: steph@zend.com ("Steph Fox") Hi Marco, > I think one of the reasons hosts don't like / use PECL is trust, they > trust > what comes with the PHP core packages and consider anything else a > security > risk. Maybe a combination of better distribution, package details, > stability > (beta / alpha) etc and maybe something that deals with compatibility. IE, > compatible with PHP 5.2.1 - 5.3.0 for example. This is precisely what I'm suggesting. Groups of extensions, classified in terms of general usefulness + stability, released alongside PHP releases (no question about compatibility that way.) In doze terms that would translate to a smaller bundle of .dlls (as opposed to the 100-ish we currently get if we download the PECL bundle), in *nix terms it would probably equate to either a group 'pecl install' command or a bundle of rpms (or both). Everyone can still use the routes they already use to get hold of the more esoteric bits and pieces, but there'd be a group of recommended extensions handy that hosts at least shouldn't be afraid to install. That in turn should make it easier for users to get those extensions enabled. Not sure how many of the > larger bulk hosting companies monitor these lists but maybe trying to > foster > more enagement from the bulk hosters in their concerns etc could be > useful? Just check the list archives. Tho' I agree it would be helpful if those same people would butt in at this point. > Again these are just the experiences I have with the hosts i've had to > deal > with whilst trying to develop an app that will run anywhere (not an easy > task I can tell you!). Not an easy task, and made harder by the fact that stuff moves in and out of core from/to a place hosts don't generally go. - Steph > > Regards > > Marco >