--- README.TESTING.orig 2005-08-08 12:08:04.000000000 -0700
+++ README.TESTING 2005-08-08 12:20:36.000000000 -0700
@@ -38,10 +38,15 @@
[Which php.ini is used]
- "make test" uses the same php.ini file as it would once installed.
-The tests have been written to be independent of that php.ini file,
-so if you find a test that is affected by a setting, please report
-this, so we can address the issue.
- "make test" uses the system default php.ini file (/etc/php.ini)
+unless it does not exist or is otherwise specified with the "-c
+[path]" argument. If a system install does not exist, the php.ini
+file that is part the distribution source code is used instead.
+The tests are supposed to have been written to be independent of that
+php.ini file, so if you find a test that is affected by a setting,
+please report this, so we can address the issue. Quite a number of tests
+do use the /etc/php.ini or specified ini file settings as of PHP 4.4.
[Which test scripts are executed]
Not quite, the default php.ini file is actually
/usr/local/lib/php(-cli).ini unless you tell PHP a custom path to
install itself or the ini to. IMHO hard coding a path into the docs is a
BAD idea.
Ilia
Rob Vaughn wrote:
--- README.TESTING.orig 2005-08-08 12:08:04.000000000 -0700
+++ README.TESTING 2005-08-08 12:20:36.000000000 -0700
@@ -38,10 +38,15 @@[Which php.ini is used]
- "make test" uses the same php.ini file as it would once installed.
-The tests have been written to be independent of that php.ini file,
-so if you find a test that is affected by a setting, please report
-this, so we can address the issue.
- "make test" uses the system default php.ini file (/etc/php.ini)
+unless it does not exist or is otherwise specified with the "-c
+[path]" argument. If a system install does not exist, the php.ini
+file that is part the distribution source code is used instead.+The tests are supposed to have been written to be independent of that
+php.ini file, so if you find a test that is affected by a setting,
+please report this, so we can address the issue. Quite a number of tests
+do use the /etc/php.ini or specified ini file settings as of PHP 4.4.[Which test scripts are executed]
Excellent (!!) point about hard-coding a path into the docs, hadn't thought of
that, doesn't apply to Windows, etc. You can clip out the reference to
/etc/php.ini and the rest is still far more clear than the current verbiage.
Ilia Alshanetsky wrote:
Not quite, the default php.ini file is actually
/usr/local/lib/php(-cli).ini unless you tell PHP a custom path to
install itself or the ini to. IMHO hard coding a path into the docs is a
BAD idea.Ilia
Rob Vaughn wrote:
--- README.TESTING.orig 2005-08-08 12:08:04.000000000 -0700
+++ README.TESTING 2005-08-08 12:20:36.000000000 -0700
@@ -38,10 +38,15 @@[Which php.ini is used]
- "make test" uses the same php.ini file as it would once installed.
-The tests have been written to be independent of that php.ini file,
-so if you find a test that is affected by a setting, please report
-this, so we can address the issue.
- "make test" uses the system default php.ini file (/etc/php.ini)
+unless it does not exist or is otherwise specified with the "-c
+[path]" argument. If a system install does not exist, the php.ini
+file that is part the distribution source code is used instead.+The tests are supposed to have been written to be independent of that
+php.ini file, so if you find a test that is affected by a setting,
+please report this, so we can address the issue. Quite a number of tests
+do use the /etc/php.ini or specified ini file settings as of PHP 4.4.[Which test scripts are executed]