Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24958 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71560 invoked by uid 1010); 25 Jul 2006 08:40:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 71545 invoked from network); 25 Jul 2006 08:40:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2006 08:40:25 -0000 X-PHP-List-Original-Sender: phil@dialsolutions.co.uk X-Host-Fingerprint: 62.245.38.178 adsl-static-3-178.uklinux.net Linux 2.5 (sometimes 2.4) (4) Received: from ([62.245.38.178:46186] helo=dialsolutions.co.uk) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 9E/C1-04178-7F8D5C44 for ; Tue, 25 Jul 2006 04:40:25 -0400 Received: (qmail 24230 invoked from network); 25 Jul 2006 08:40:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on xeon.morritt.dialsolutions.net X-Spam-Level: X-Spam-Status: No, score=-101.8 required=3.0 tests=ALL_TRUSTED,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.1.0 Received: from unknown (HELO opteron.morritt.dialsolutions.net) (192.168.2.20) by 0 with SMTP; 25 Jul 2006 08:40:10 -0000 To: internals@lists.php.net Date: Tue, 25 Jul 2006 09:40:10 +0100 User-Agent: KMail/1.9.1 References: <2a9adcf0607240752k12eb8f32sd753eaadaac6e8cc@mail.gmail.com> <2a9adcf0607241018o3afce85dk28b3fa794a2442fd@mail.gmail.com> <06c801c6af4a$442c1c20$6602a8c0@foxbox> In-Reply-To: <06c801c6af4a$442c1c20$6602a8c0@foxbox> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200607250940.10277.phil@dialsolutions.co.uk> Subject: Re: [PHP-DEV] New Installer for PHP 5.2 From: phil@dialsolutions.co.uk (Phil Driscoll) On Monday 24 July 2006 18:54, Steph Fox wrote: > httpd.conf's weird? It's only a text file :) the complication's in the fact > that there's more than one way to set it up. But you could offer automated > basic CGI setups pretty easily using the paths you've already been given > for php.exe and php.ini, and the module setup actually isn't that > complicated either, assuming you already know it's an apache module setup > that's required. 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. Can anyone think of a slick way of dealing with this (and ideally one which can be implemented from within Wix? -- Phil Driscoll