When you build the Apache2 SAPI the only binary build is the module, so
'--program-suffix' is unused. Anyway it doesn't have to be the same
configuration option per say (though I don't see why not), but the
method of specifying the suffix with configure is much handier than
having it hard-coded in source. I've stated the reasons in the previous
e-mail.
Best regards,
Arnold
Jani Taskinen wrote:
Because it's --program-suffix and not --library-suffix.
--Jani
On Fri, 2007-06-01 at 11:29 +0200, Arnold Daniels wrote:
Hi,
Why isn't the Apache module appended with the same suffix as the other
binaries (configuration option --program-suffix). It seems like the
logical solution here. That way you can have any different versions if
you want, but the default is just the overwrite.
Best regards,
Arnold
Stanislav Malyshev wrote:
I'd rather not have my old libphp#.so file over-written when I install
a new version, in case things go horribly wrong and I want to just
roll-back...
Then you have the same reason to worry right now - every php5 install
from 5.0.0 to 5.2.3 overwrites libphp5.so.
There was a time where one could have 2 php mod versions running at
once, as I recall, and having different filenames was kinda important,
eh?
Well, there was a setting that kinda allowed that, but I'm not sure it
ever worked correctly - there are all sorts of symbol clashes, etc.
On the other hand, you can happily run two (or a dozen :) PHP versions
right now - just install any FastCGI implementation, compile two
cgi-fcgi PHPs and install. Only thing you would need to care about is
to give them separate php.ini's and/or separate extension directories.
