Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53069
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.187 cause and error)
Message-ID: <4DED206F.5040204@lsces.co.uk>
Date: Mon, 06 Jun 2011 19:46:07 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-2.2 SeaMonkey/2.0.14
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <4DE7F179.5010402@sugarcrm.com>	<alpine.DEB.2.02.1106030920570.9040@whisky>	<4DE89CD2.4040302@sugarcrm.com>	<alpine.DEB.2.02.1106030937571.9040@whisky>	<4DE9AA9B.3000108@sugarcrm.com>	<BANLkTinxwduQXxBoLZuFzT_Wyfy-LGC6ZA@mail.gmail.com>	<slrniunu3j.dic.dsp@experimentalworks.net>	<4DEC02B6.60806@sugarcrm.com>	<4DEC7FED.9000700@lsces.co.uk>	<4DEC8570.1010904@sugarcrm.com>	<4DECACFB.5000805@lsces.co.uk>	<BANLkTinv4Lg+KW-6e1RRygZc3aFeZzPEdQ@mail.gmail.com>	<4DECBE94.7010502@lsces.co.uk>	<BANLkTikvu_krucNLtYbuSRxN7+_+4qNvEA@mail.gmail.com>	<4DECD6BC.5050101@lsces.co.uk>	<BANLkTi=WTOS4A=jOK+KaaXE0it=ePYwwjQ@mail.gmail.com>	<4DECFC84.3080800@lsces.co.uk>	<BANLkTimvdhwzk3GDJUDdTS+CQi_NYmD+hQ@mail.gmail.com>	<4DED04EC.2040907@lsces.co.uk>	<BANLkTimh3SF8txJJzMLxvCzSge+U7P+fMw@mail.gmail.com>	<4DED0A9A.80202@lsces.co.uk>	<BANLkTinhnkK6_8NDNVZ9+wyvOkVoF7o35Q@mail.gmail.com>	<4DED1854.5040106@lsces.co.uk> <BANLkTi=GerD0-mHkNc0BHZRwVL+8oHCNvw@mail.gmail.com>
In-Reply-To: <BANLkTi=GerD0-mHkNc0BHZRwVL+8oHCNvw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 5.4 moving forward
From: lester@lsces.co.uk (Lester Caine)

Pierre Joye wrote:
> However I ask you, strongly, now to stop to pollute this thread with
> totally unrelated topics. Thanks for your understanding.

This is something of a rather important point since PHP has always been very 
strongly related to Apache so it is totally related to a discussion of moving 
PHP forward. Currently the mainstream information is so far adrift of the 
present situation that at it needs to be addressed. A starting point would be to 
bring all of the PHP manual information in line with the current situation and 
point people to the preferred installation paths rather than telling people to 
use steps that do not actually get to a working PHP5.3 setup? And starting to 
push out 5.4 will increase peoples requests to getting things working with 
exiting windows/apache/php5.2 setups.

Does anybody other than Pierre disagree with the point that currently the 
mainstream windows installation paths are something of a mess and needs to be 
updated in some way?

I've been updating my own installation guides, but I had not realised just how 
many other PHP projects provide windows installation guides that no longer work. 
Not having been using windows myself on new builds for some time, I had not 
updated and tested clean installs and it's only recently I've found how out of 
date things are :( I've been getting emails from people asking why my guides 
were not working hence the need to address this and get back to a working situation.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php