Extending SAPI specific php.ini to include, at least, major version.

php.internals

Richard Quadling

20 years ago
Hi. The ability to create a SAPI specific php.ini file (php-cli.ini, php-isapi.ini, etc) for PHP5 is excellent. This allows me to run PHP4 as CGI and PHP5 as ISAPI on the same webserver (I use Sambar Server). Now that I'm starting to look at PHP6, I would like to run PHP4, PHP5 AND PHP6 on the same web server (yes - I'm a greedy glutton). But the issue of having the same php.ini for PHP5 and PHP6 (both are php-isapi.ini) is a pain and stops me from playing with them together. If php_ini.c (/* $Id: php_ini.c,v 1.142 2006/03/08 14:41:45 iliaa Exp $ */) Lines 431 to 440 could be extended to include the major version number, then we could have php5-cli.ini, php5-isapi.ini php6-cli.ini, php6-isapi.ini My next issue would relate to how the webserver picks up the DLLs and gets them into usage. Is it just on the internal function names? If so, I think I'll have an issue here too if the names are the same - and I can initially see no reason why they won't be the same. Kind regards, Richard Quadling.
-- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731

D. Dante Lorenso

20 years ago
Richard Quadling wrote:
> But the issue of having the same php.ini for PHP5 and PHP6 (both are > php-isapi.ini) is a pain and stops me from playing with them together.
Can't you just configure PHP when you compile it with the following option: ./configure ... --with-config-file-path=/path/to/php6ini/ \ ... Then specify your own PHP ini search path and use different ones for each version you compile. No changes to PHP, and your problem is solved. Dante

Richard Quadling

20 years ago
Sorry. I forgot to mention, I'm talking about the Windows pre-compiled versions of PHP. With Sambar Server, only the dll is recorded. There is no opportunity to supply any additional parameters. Another alternative would be to allow the single INI file have PHP5 and PHP6 entries. Essentially, for me, it is the extension directory. As you cannot load a PHP6 extension into PHP5 or vice-versa, having to indicate which directory contains the extensions is important. Sorry for the lack of info on this. Richard. D. Dante Lorenso wrote: