On Thu, 2014-05-08 at 23:20 +0200, Martin Keckeis wrote:
> Am 07.05.2014 15:18 schrieb "Andrea Faulds" <[email protected]>:
> >
> >
> > On 7 May 2014, at 14:13, Jan Ehrhardt <[email protected]> wrote:
> >
> > > Zeev Suraski in php.internals (Wed, 7 May 2014 09:36:14 +0300):
> > >> Seriously, I can't think of any *real* reason of why anybody would
> > >> need something other than these SAPIs in 2014 (other than FUD).
> > >> Things like ISAPI and other more esoteric SAPIs are no brainers, and
> > >> while mod_php may be a bit more of a leap of faith, it doesn't truly
> > >> brings any tangible benefits over FastCGI (none that can't be
> > >> relatively easily replicated in userland anyway, eg htscanner).
> > >
> > > Is Fastcgi capable of supporting 2 versions of PHP? I still need PHP 5.3
> > > for Drupal6, but Drupal7, Wordpress, Modx and the like profit from PHP
> > > 5.5. If there was a way to run both versions as Fastcgi, I would happily
> > > go along with you. But I haven't found out how to do that, so one of
> > > the two still is mod_php.
> >
> >
> > Correct me if I’m wrong, but don’t you simply need to have two PHP
> > versions installed (5.3 FastCGI and 5.5 FastCGI) and then reference the
> > appropriate ones in your server configuration files? The hard bit would be
> > the dual installation (you’d probably need to build from source), but
> > having the web server handle both should be trivial.
If there is need is relatively easy for distributors to provide
different versions installed to different locations. They can't easily
enable both in the server, though, and the user has to configure vhosts
or such, which is quite obvious.
> The only problem is when you need the "php" global command for both
> versions...
Either have only one in $PATH and use absolute path for the other or
give explicit names. i.e. by symlinks. Distributions could easily create
such a setup:
/usr/bin/php55 -> /usr/php55/bin/php
/usr/bin/php56 -> /usr/php56/bin/php
/usr/bin/php -> /etc/alternatives/php
johannes