>>> The problem (and the thing which put me off tackling this on the current
>>> windows installer) is that there are so many ways that a use could have
>>> already set up their httpd.conf (with regard to global and vhost
>>> configurations, whether httpd.conf does all the config, or there are
>>> include
>>> files and .htaccess files doing things), the installer would need to
>>> more or
>>> less fully understand apache configuration rules to be able to (a) make
>>> sure
>>> that php was working at the end of the install, and (b) nothing else was
>>> broken. It would also probably need a massive user interface in order to
>>> deal
>>> with the many decisions which would need to be made in order to work out
>>> precisely what to do.
I do agree with Phil here; the last thing we would want is to leave
extra junk in the user's http.conf, nor we want to "break things"
because they have different things enabled, thus resulting in a
non-working install.
Personally, I like the approach many Linux distros ( Ubuntu is one
that I've seen do this ) is instead of one monolithic httpd.conf file,
they have it include the configuration for the various modules
seperately so that they can add and remove the config code cleanly.
That I could see working well; you'd still have the risk of a
non-working install, but making it work again is simply commenting out
one line.
Steph, do you think this approach would work?
--
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
