Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:31025 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74266 invoked by uid 1010); 17 Jul 2007 21:12:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 74251 invoked from network); 17 Jul 2007 21:12:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jul 2007 21:12:52 -0000 Authentication-Results: pb1.pair.com header.from=info@adaniels.nl; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=info@adaniels.nl; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain adaniels.nl from 82.94.236.173 cause and error) X-PHP-List-Original-Sender: info@adaniels.nl X-Host-Fingerprint: 82.94.236.173 loco.helderhosting.nl Linux 2.5 (sometimes 2.4) (4) Received: from [82.94.236.173] ([82.94.236.173:49045] helo=loco.helderhosting.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 66/02-59838-2D03D964 for ; Tue, 17 Jul 2007 17:12:52 -0400 Received: from [192.168.2.13] (bas3-toronto01-1177778256.dsl.bell.ca [70.51.120.80]) by loco (Postfix) with ESMTP id 623F110D8838; Tue, 17 Jul 2007 23:12:45 +0200 (CEST) Message-ID: <469D30DA.8020209@adaniels.nl> Date: Tue, 17 Jul 2007 17:12:58 -0400 User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Rasmus Lerdorf Cc: PHP Developers Mailing List References: <469D03D1.1060508@lerdorf.com> <469D14A2.3010805@sci.fi> <469D1C2E.9080505@lerdorf.com> <9981B5C3-E9AC-4105-845C-C828FD474089@wanderingknights.org> <469D2529.9050307@lerdorf.com> <469D2890.8060904@adaniels.nl> <469D2B3B.1080601@lerdorf.com> In-Reply-To: <469D2B3B.1080601@lerdorf.com> Content-Type: multipart/alternative; boundary="------------050109080208000404000408" Subject: Re: [PHP-DEV] Nifty feature From: info@adaniels.nl (Arnold Daniels) --------------050109080208000404000408 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I understand, but Yahoo is huge. We are not... Saying that it is standard practice for ISP's is perhaps (ehh for sure) a bit of an overstatement, since I only have contact with other small hosting providers like us. For us making packages actually takes up a significant amount of time, so creating a different package for everything is simply not feasible. Also all our web servers have the same configuration (luckily). Anyway, I only mend to say that building pecl packages in the PHP distro isn't so rare as just claimed. So it would be nice if this nifty feature would also work for added packages. Best regards, Arnold Rasmus Lerdorf wrote: > Arnold Daniels wrote: > >> Hi Rasmus, >> >> I hope you've got a lot of fingers on your hand, because we do this as well. >> >> All servers are updated with an apt script and our private repository. >> It's easier to manage a single php package on all servers, that 14 >> different packages. Each time PHP updates we take the newest packages >> from pecl and sometimes if PHP isn't updated for a more than a month, we >> might make a build with the same PHP version but new pecl packages. >> >> To my knowledge this is standard practice for ISP's (who build PHP them >> selfs). I haven't heard of anyone actually using `pecl update` to >> update. Most ISP's just update the whole thing one each week, month, >> year, decade. >> > > I'm not talking about pecl update. I never use that either. The way we > do it at Yahoo, and the way the distros do it, is to create separate > packages for as many things as possible such that in order to quickly > update any component we can do it with the lowest impact possible. Not > all servers have all the PHP-related packages installed, obviously, so > if there is a critical update to a specific package we can limit it to > just the affected servers. > > -Rasmus > --------------050109080208000404000408--