(php) Impossible to install two versions of PHP about chocolatey-packages

[ferventcoder]

Likely.

[ferventcoder]

Is PHP like Ruby in that it can be installed multiple times?

[laurinkeithdavis]

Yes.

[ferventcoder]

@majkinetor created chocolatey-community/chocolatey-packages#425 to address this.

[ferventcoder]

We'll keep it open here until it is implemented there.

[majkinetor]

@ferventcoder, can I recognize the -m switch from within chocolateyInstaller ?

[ferventcoder]

Nada - the trick is usually to explicitly set the install directory to php### where # is the accepted versioning convention that is most widely used - for instance it could be 5.4 or 5.4.x and then 5.5. I am not typically using php so I don't know what that should look like.

In Ruby it is:

• Ruby1.8.7
• Ruby1.9.3
• Ruby2.0.0
• Ruby2.1
• Ruby2.3

Or something like that. Away from my computer at the moment, the versioning changed after 2.0.0 to be more SemVer compliant (at least in numbering).

[majkinetor]

Rob, that is not the problem. I already did the same thing for python. The problem is how to handle existing users on update. My plan was to still install to the old location if you don't care for multiple versions. Since that is not possible installer code would have to check for older installation.

[ferventcoder]

usually folks use -m (or side by side installs) and then they pin those installs so they don't upgrade. There is a better story for upgrades in that kind of set up coming later.

[photodude]

I'm assuming this issue can be closed now that @AdmiringWorm has push chocolatey-community/chocolatey-packages#548 with the function for this