Miroslav Lachman wrote:
I guess that mod_php5 depends on Apache and maintainer don't want this
big dependency. The second is - if it will depends on Apache of some
version (eg. 1.3) it will be broken with another version (2.0 and 2.2).
It apply for binary packages. If somebody is compiling por
Christopher Hilton wrote:
Jonathan Horne wrote:
[...]
Everyone seems to be misunderstanding my question. I'm aware of how to
build mod_php5. I'm curious about why the default configuration builds
php5 as a standalone CLI and CGI rather than as an apache module. I'm
assuming that there is s
Jonathan Horne wrote:
Bob wrote:
The php4 & php5 port apache module used to be default before FBSD 6.0.
Many people before you on this list have wanted the php4/5 apache module
turned back on as default but so far the port maintainer has not done
anything
in any way of justifying removing the ap
> Bob wrote:
>> The php4 & php5 port apache module used to be default before FBSD 6.0.
>> Many people before you on this list have wanted the php4/5 apache module
>> turned back on as default but so far the port maintainer has not done
>> anything
>> in any way of justifying removing the apache mod
On Saturday 09 June 2007 14:13:10 Christopher Hilton wrote:
> Bob wrote:
> > The php4 & php5 port apache module used to be default before FBSD 6.0.
> > Many people before you on this list have wanted the php4/5 apache module
> > turned back on as default but so far the port maintainer has not done
Bob wrote:
The php4 & php5 port apache module used to be default before FBSD 6.0.
Many people before you on this list have wanted the php4/5 apache module
turned back on as default but so far the port maintainer has not done
anything
in any way of justifying removing the apache module from the de
.org; User Questions
Subject: Php5 port and Apache Module
I can see that if I build the php5 port it defaults to CLI and CGI mode
but the Apache module is not built. Am I wrong when I assume that the
Apache Module will have the best performance? I guess that I'd just like
to understand the en
I can see that if I build the php5 port it defaults to CLI and CGI mode
but the Apache module is not built. Am I wrong when I assume that the
Apache Module will have the best performance? I guess that I'd just like
to understand the engineering decisions behind the default in the port's
configu
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher Hilton
Sent: 9 juin 2007 15:51
To: freebsd-ports@freebsd.org; User Questions
Subject: Php5 port and Apache Module
I can see that if I build the php5 port it defaults to CLI and CGI mode
but
