> Nice done;-)
Thanks!
> I only had a brief look, but following comes to my mind:
> Manual Installation Steps:
> I would like to advice people to use php-(sapiname).ini or at least
mention
> this somewhere.
> I like to suggest that setup of a valid php.ini file is moved to the
server
> specific instructions. Because one can run php just fine without any
> ini-file, you need this mainly for enabling extensions, or setting
specific
> instructions.
Oh yes, I need to document the php-{sapi}.ini
> Windows and PWS 4 or newer
>
> Instructions for php 5 are missing, filenames imply its for php 4 only
(e.g.:
> pws-php4cgi.reg)
>
> Same for Windows NT/2000/XP and IIS 4 or newer (e.g: php4isapi.dll)
>
> At the latest reading the instructions for IIS/PWS it is not clear to me,
> where the ini-file should go, therefore my above suggestion to provide
this
> sort of info perhaps in the server specific instructions ( at keast for
the
> sapi modules)
>
> Don't take this offending, jst a few thoughts after a very quick look;-)
Of course, no offending :) I haven't touch the IIS/PWS section. I can
install IIS tomorrow to test...
> > And if yes, can I do the change to the new install section
>
> IMHO commit your nice work to the new install section, once it is there it
can
> be easily reviewed and tweaked up, if needed.
OK, I'll commit it in a minute (with several fixes noticed by Goba).
It's already late now, but I'll review the docs tomorrow.
> > (including
> > removing the old chapters/instal./.xml)?
>
> There's no hurry to remove the old files;-)
The hurry is just because 'make test' will fail if you don't delete those
files (because of ID colisions)
Nuno
