Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30029
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.171 cause and error)
Message-ID: <46602120.7020900@sci.fi>
Date: Fri, 01 Jun 2007 16:37:36 +0300
Reply-To:  jani.taskinen@iki.fi
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Arnold Daniels <info@adaniels.nl>
CC:  jani.taskinen@iki.fi, 'PHP Internals' <internals@lists.php.net>
References: <465E00E2.4010905@zend.com> <465E08D9.4020101@sci.fi>	 <465E7A28.3010100@zend.com> <465E8F99.70407@sci.fi>	 <49250.216.230.84.67.1180642728.squirrel@www.l-i-e.com>	 <465F305A.9020902@zend.com>  <465FE701.6080401@adaniels.nl> <1180695997.3481.2.camel@localhost.localdomain> <46600C59.1010406@adaniels.nl>
In-Reply-To: <46600C59.1010406@adaniels.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 5 or 6?
From: jani.taskinen@sci.fi (Jani Taskinen)

It's actually not the only binary/script that is build.
--program-suffix|prefix affect also phpize, etc. scripts names.
And AFAIK, CLI binary is always build unless of course you disable it. :)

Patches are welcome.

--Jani

Arnold Daniels kirjoitti:
> When you build the Apache2 SAPI the only binary build is the module, so 
> '--program-suffix' is unused. Anyway it doesn't have to be the same 
> configuration option per say (though I don't see why not), but the 
> method of specifying the suffix with configure is much handier than 
> having it hard-coded in source. I've stated the reasons in the previous 
> e-mail.
> 
> Best regards,
> Arnold
> 
> 
> Jani Taskinen wrote:
>> Because it's --program-suffix and not --library-suffix.
>>
>> --Jani
>>
>> On Fri, 2007-06-01 at 11:29 +0200, Arnold Daniels wrote:
>>   
>>> Hi,
>>>
>>> Why isn't the Apache module appended with the same suffix as the other 
>>> binaries (configuration option --program-suffix). It seems like the 
>>> logical solution here. That way you can have any different versions if 
>>> you want, but the default is just the overwrite.
>>>
>>> Best regards,
>>> Arnold
>>>
>>>
>>>
>>> Stanislav Malyshev wrote:
>>>     
>>>>> I'd rather not have my old libphp#.so file over-written when I install
>>>>> a new version, in case things go horribly wrong and I want to just
>>>>> roll-back...
>>>>>         
>>>> Then you have the same reason to worry right now - every php5 install 
>>>> from 5.0.0 to 5.2.3 overwrites libphp5.so.
>>>>
>>>>       
>>>>> There was a time where one could have 2 php mod versions running at
>>>>> once, as I recall, and having different filenames was kinda important,
>>>>> eh?
>>>>>         
>>>> Well, there was a setting that kinda allowed that, but I'm not sure it 
>>>> ever worked correctly - there are all sorts of symbol clashes, etc.
>>>>
>>>> On the other hand, you can happily run two (or a dozen :) PHP versions 
>>>> right now - just install any FastCGI implementation, compile two 
>>>> cgi-fcgi PHPs and install. Only thing you would need to care about is 
>>>> to give them separate php.ini's and/or separate extension directories.
>>>>       
>>
>>