Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31018
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain adaniels.nl from 82.94.236.173 cause and error)
Message-ID: <469D2890.8060904@adaniels.nl>
Date: Tue, 17 Jul 2007 16:37:36 -0400
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Gwynne Raskind <gwynne@wanderingknights.org>,
	PHP Developers Mailing List <internals@lists.php.net>
References: <469D03D1.1060508@lerdorf.com> <469D14A2.3010805@sci.fi> <469D1C2E.9080505@lerdorf.com> <9981B5C3-E9AC-4105-845C-C828FD474089@wanderingknights.org> <469D2529.9050307@lerdorf.com>
In-Reply-To: <469D2529.9050307@lerdorf.com>
Content-Type: multipart/alternative;
 boundary="------------050505080106050908050605"
Subject: Re: [PHP-DEV] Nifty feature
From: info@adaniels.nl (Arnold Daniels)

--------------050505080106050908050605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

Best regards,
Arnold


Rasmus Lerdorf wrote:
> Gwynne Raskind wrote:
>   
>> On Jul 17, 2007, at 3:44 PM, Rasmus Lerdorf wrote:
>>     
>>>>> Hey Jani, nice job on the unknown configure options check.  I saw the
>>>>> commit go through a couple of days ago, and today it got me to clean up
>>>>> an ancient build script I have been using for ages when it gave me
>>>>> this:
>>>>>
>>>>> Notice: Following unknown configure options were used:
>>>>>
>>>>> --with-pdflib=/usr/local
>>>>> --enable-gd-imgstrttf
>>>>> --with-expat=/usr
>>>>> --with-xmlreader
>>>>>
>>>>> Check './configure --help' for available options
>>>>>           
>>>> This is exactly why I added it. :)
>>>>
>>>> Only side-effect is that any 3rd party extension which happens to use
>>>> the AC_ARG_* macros will cause it to report those as "unknown". But
>>>> perhaps it's time to be update.. ;)
>>>>
>>>> *cough* APC *cough*
>>>>         
>>> But this check isn't in a phpize-generated configure script, so I don't
>>> see how this is a problem.  The number of people who build pecl
>>> extensions in the main source tree can probably be counted on one hand.
>>>       
>> *raises hand* I do... all the time. *crawls back under her rock*
>>     
>
> Can you explain why?  I find it much easier to build the non-core stuff
> separately so I can update either without affecting the other.
>
> -Rasmus
>
>   

--------------050505080106050908050605--