Re: [PHP-DEV] [WARNING] Release process for 4.3.2 starts RSN..
Any progress towards a 4.3.2 release? Cheers ..Petar - Original Message - From: Jani Taskinen [EMAIL PROTECTED] To: Shane Caraveo [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, February 24, 2003 10:13 AM Subject: Re: [PHP-DEV] [WARNING] Release process for 4.3.2 starts RSN.. snip Jani Taskinen wrote: To get this thing started, I'm going to roll PHP 4.3.2-pre1 on Wednesday, 26th Feb, around 3pm EEST. And I'll announce it on php-general too, to get some more people testing it before we start with any RCs. Following is collection of bugs marked as critical and verified which should be looked into and dealt with. If not fixed, then please, PLEASE add some comment why they won't ever be fixed and bogus the out. snip -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] win32 php.ini default behavior better in php executable directory?
Hi All, Sorry about the cross post but I suppose it applies in both areas. I raised a few questions about getting an alternate php.ini recognised when multiple php installs are on a windows 2000 server with no real solution so far. I noticed 4.3.0 claims to have support for the -c /path/to/php.ini which should allow the cgi version to use an alternate php.ini file but it does not work under IIS5 and neither does 4.2.3 I propose that the initial location php.exe should look for a php.ini file is in the directory from which it executes. This would overcome any issues with individual web servers on a win32 platform and allow multiple configs/multiple copies of php to be executed without trickery like the -c /path/to/php.ini which doesn't work. I could then run a d:\client1\phpbin and e:\client2\phpbin without any additional support required by the webserver. The size of php is tiny and would not be an impost to run multiple copies. This system would allow multiple version to run if required by simply changing the cirtual directory structure in IIS5. To keep the present 'default' behavior just make sure you don't keep a php.ini in the executable directory and it should then run off and look in c:\winnt like it does at present. Anyone see a downside to this proposition? Regards ..Petar -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
