Hi there,
On 7/26/06, Steph Fox <[EMAIL PROTECTED]> wrote:
The php.ini file, on completion, needs to be copied to one with the relevant
SAPI name. In the case of Apache 1 only, php-apache.ini needs to be in the
toplevel Apache directory. In every other case (php-cli.ini,
php-cgi-fcgi.ini php-apache2.ini, and php-whatever-2.2-SAPI-is-called.ini)
it needs to be in the PHP install dir. That means the only chance of having
a meaningful collision with an existing PHP installation is via the Apache 1
module, thanks to the placement of that .ini file.
I've never that noticed back when I was running Apache 1; would having
the php.ini in the Windows PATH or setting PHPRC help this any?
Either pair of lines could potentially break an existing PHP setup, sure.
But given that the mime type declaration and DirectoryIndex list can't break
anything, effectively you're advocating one line and an extra file instead
of two lines here - and all four lines at least begin with the same thing
every time no matter how you may have installed them previously:
ScriptAlias /php/
Action application/x-httpd-php
PHPIniDir
LoadModule php5_module
So, would it be possible to check httpd.conf for those lines and notify in
the case of a conflicting install request?
'Uninstall' would just mean deleting those two lines, not the mime type
support or the directory index entry.
Thanks for the simplification and research; being able to put all of
this at the end is very good to know.
I still prefer the method of including a file instead of altering the
httpd.conf file; it's cleaner and easier to rollback on an uninstall.
And I'm not sure I want to go as far as trying to undo or correct
previous PHP setting in there either; I'll make the include file
assume we are working with a stock httpd.conf file and if the user has
previous directives it's thier responsibility to correct them.
I do think it should be made clear that this is a global install on the
Apache server and that anything more complex (vhosts or whatever) needs to
be done manually. I didn't see any obvious way to open a file for editing
from within a wix installer though - is that possible or not?
This isn't directly possible, but you can create call external scripts
to do this ( this is how IIS is configured ). Probably I'd do the same
here.
--
Later,
John Mertic
"Explaining a joke is like dissecting a frog: you
[EMAIL PROTECTED] understand it
better, but the frog dies in the
process."
-Mark Twain
--
Later,
John Mertic
"Explaining a joke is like dissecting a frog: you
[EMAIL PROTECTED] understand it
better, but the frog dies in the
process."
-Mark Twain
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
