Edit report at https://bugs.php.net/bug.php?id=50583&edit=1
ID: 50583
Updated by: paj...@php.net
Reported by: ksingla at microsoft dot com
Summary: PHP Installer needs to support side by side
installlation of 5.2 and 5.3 version
-Status: Assigned
+Status: Wont fix
Type: Bug
Package: Windows Installer
Operating System: Windows
PHP Version: 5.3.1
Assigned To: pajoye
Block user comment: N
Private report: N
New Comment:
installer is not supported anymore in 5.3 and later.
Previous Comments:
------------------------------------------------------------------------
[2010-04-16 10:59:40] paj...@php.net
This plan can only partially work for what we described and need. That's not
what we can or will implement.
Taking the hand over that one. I will discuss with John about the possible
solutions and get them into our roadmap.
------------------------------------------------------------------------
[2010-04-15 20:47:37] rusl...@php.net
The proposed plan for enabling this is described below:
1. Choose different upgrade codes for PHP 5.2, PHP 5.3 and PHP 6.0
2. Use folder php52, php53 or php60 under %programfiles% for copying files
instead of fixed one %programfiles%\php.
3. Use different registry paths for different versions.
4. Do not set PHPRC environment variable at system level. This is required
to make different versions of PHP pick different php.ini in a SxS environment
for non-FastCGI SAPI's. This request is tracked by a separate bug:
http://bugs.php.net/bug.php?id=51536.
5. Add detection mechanism to detect if other versions are installed. If
so, show a warning message telling people to uninstall and then install if they
don't want SxS install. Also say that php.ini configuration of other version
won't be picked when SxS is happening.
------------------------------------------------------------------------
[2010-03-25 18:53:48] jmer...@php.net
Currently assessing whether we can do this across all SAPIs or not.
------------------------------------------------------------------------
[2010-01-21 21:21:15] ruslany at microsoft dot com
In addition to that it would be nice if PHP installer allowed user to choose
whether to upgrade an existing PHP installation or install a new version side
by side. For example, on the very first page of the installer there can be
options presented:
1. Upgrade existing installation
2. Install side-by-side and make this a default version
3. Install side-by-side but keep existing version as a default.
In case of installing on IIS that would mean:
In #1 the installer will upgrade the PHP installation as it does today.
In #2 the installer will install binaries into a new folder and then configure
FastCGI handler mapping on a server level and make it the top in the handler
mapping list so that it is used by all sites.
In #3 the installer will install binaries into a new folder, configure FastCGI
handler mapping, but will not re-order the existing FastCGI handler mapping so
that previosly installed PHP vesion is still used.
------------------------------------------------------------------------
[2009-12-26 23:28:17] ksingla at microsoft dot com
Description:
------------
In order to support side-by-side installation of PHP 5.2 and 5.3 by Microsoft
Web Platform Installer, PHP installer needs to support side by side setup. To
get to a version specific installation, I think following changes will be
required
a. Currently, PHP is installed to %PROGRAMFILES(X86)%\PHP or
%PROGRAMFILES%\PHP. This should change to %PROGRAMFILES(X86)%\PHP\<version> or
%PROGRAMFILES%\PHP\<version>
b. Currently PHP sets the following registry keys:
i. HKLM\SOFTWARE\Wow6432Node\PHP on 64-bit systems.
ii. HKLM\SOFTWARE\PHP on 32-bit systemsc.
Change the registry keys to:
i. HKLM\SOFTWARE\Wow6432Node\PHP\<version> on 64-bit systems.
ii. HKLM\SOFTWARE\PHP on 32-bit systems\<version>d. Set an environment
variable called PHPLOC with the path to the latest installed PHP
c. When IIS-FastCGI install is selected, installer should let users add the PHP
handler at site or application level as well so that a particular PHP version
can be used for that site or application. Currently the handler is always added
at the server level.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=50583&edit=1
