Re: Windows installer
| From: | Hellekin O. Wolf | Date: | Fri, 18 Aug 2000 08:43:33 +0000 |
| Subject: | Re: Windows installer | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-764@lists.php.net to get a copy of this message | ||
Phil Driscoll wrote:
>
> I've done (I think!) everything apart from the sordid business of
> configuring the IIS metabase.
>
> At http://www.dialsolutions.com/phil/php/installer/
>
> there are screenshots of the install wizard in action.
>
*** Great...
I have a few remarks on the ergonomics.
1. Would it be possible to separate a "BASIC" default install from an
"ADVANCED" install ?
The BASIC install would only prompt for the php directory, then do
everything from backup, install default options. If a php.ini is
spotted, it is renamed php.ini_OLD and a new one is put (in order to
prevent bad, deprecated options to be kept and new ones not to appear).
The ADVANCED install is what you show =8)
2. When you spot an existing php.ini, would it be possible to default on
"Keep It" instead of "Replace it" ?
3. The installer should generate a PHP_INSTALL_REPORT stating the
version, the style of install (Basic or Advanced), the options chosen,
the pathes and files...
BASIC and ADVANCED Installs would be practical for testing the new
release, then rolling back, or new users on the one hand, and people who
want (almost) everything under control on the other hand.
Hope that helps.
how