Improvements and glitches for make test
[email protected] (Miroslav KubelĂk - seznam) Thu, 22 Apr 2010 13:04:06 +0300
| Newsgroups | php.pecl.dev |
|---|---|
| Organization | Home email |
| Message-ID | <[email protected]> |
Hello, when I have started to develop extensions (one year ago) with phpize, there was no possibility to use another php.ini unless default (which is specified via ./configure for whole php installation). This made problem when "make test" was used in new extension development dir. PHP complained for extensions which was specified in default php.ini and weren't in "modules" subdir under new extension dir. So I had to copy all my "productions" extensions to every "modules" subdir under each newly developed extension dir. When I upgrade to 5.3.2, there is newly created tmp-php.ini always when I type phpize, this isn't mentioned anywhere (maybe I overlooked?). Is this a fix? Is used for phpized "make test"? And in 5.3.2 is a new glitch with "make test" and phpize. Everytime when test fails, there is a request for sending response to QA with test result. I don't remember this is 5.3.0-1 and with phpize (extension development) it doesn't make sense to send result of my extension tests to QA. Regards M. Kubelik