On Thu, 27 Jul 2006, William A. Rowe, Jr. wrote:
> Given that there is significant interest, and no objection, I'll
> commit this later today. Are any of trunk / 5.2 or 4.4 branches
> frozen right now?
You can't add it to the 4.4 branch now, you'll have to wait until after
the 4.4.3 release.
r
Given that there is significant interest, and no objection, I'll
commit this later today. Are any of trunk / 5.2 or 4.4 branches
frozen right now?
Bill
Steph Fox wrote:
Steph Fox wrote:
It wouldn't make any difference to John, since he'd need to support
older Apache installs for the instal
Steph Fox wrote:
It wouldn't make any difference to John, since he'd need to support
older Apache installs for the installer anyway... apart from that,
it's got my vote!
Sure it would. PHPIniDir is apache directive provided by php's
sapi/apache2*. Adding it to sapi/apache would make it univers
Steph Fox wrote:
>
> It wouldn't make any difference to John, since he'd need to support
> older Apache installs for the installer anyway... apart from that,
> it's got my vote!
>
Sure it would. PHPIniDir is apache directive provided by php's
sapi/apache2*. Adding it to sapi/apache would make it un
Hi William,
John Mertic wrote:
Hi there,
On 7/26/06, Steph Fox <[EMAIL PROTECTED]> wrote:
In the case of Apache 1 only, php-apache.ini needs to be in the
toplevel Apache directory. In every other case (php-cli.ini,
php-cgi-fcgi.ini php-apache2.ini, and
php-whatever-2.2-SAPI-is-called.ini)
it
Hi there,
On 7/26/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
I've offered this patch before to provide the PHPIniDir for the Apache 1.3
SAPI - no response. Are people interested in my reintroducing it?
If it's fairly low risk, why not. It would make this much easier.
What does e
John Mertic wrote:
Hi there,
On 7/26/06, Steph Fox <[EMAIL PROTECTED]> wrote:
In the case of Apache 1 only, php-apache.ini needs to be in the
toplevel Apache directory. In every other case (php-cli.ini,
php-cgi-fcgi.ini php-apache2.ini, and
php-whatever-2.2-SAPI-is-called.ini)
it needs to be
Hi there,
On 7/26/06, Steph Fox <[EMAIL PROTECTED]> wrote:
>> Erm, the only way I know to include a file in httpd.conf is to use the
>> ResourceConfig file (conf/srm.conf), so I'm not sure how overwriting that
>> helps... am I missing something?
>
> Check out this:
>
> http://httpd.apache.org/do
Erm, the only way I know to include a file in httpd.conf is to use the
ResourceConfig file (conf/srm.conf), so I'm not sure how overwriting that
helps... am I missing something?
Check out this:
http://httpd.apache.org/docs/1.3/mod/core.html#include
Aha!
> And I'm not sure I want to go as fa
Hi there,
>> So, would it be possible to check httpd.conf for those lines and notify
>> in
>> the case of a conflicting install request?
>>
>> 'Uninstall' would just mean deleting those two lines, not the mime type
>> support or the directory index entry.
>
> I still prefer the method of includin
Hi there,
On 7/26/06, Steph Fox <[EMAIL PROTECTED]> wrote:
The php.ini file, on completion, needs to be copied to one with the relevant
SAPI name. In the case of Apache 1 only, php-apache.ini needs to be in the
toplevel Apache directory. In every other case (php-cli.ini,
php-cgi-fcgi.ini php-apa
>>> The problem (and the thing which put me off tackling this on the
>>> current
>>> windows installer) is that there are so many ways that a use could
>>> have
>>> already set up their httpd.conf (with regard to global and vhost
>>> configurations, whether httpd.conf does all the config, or the
>>> The problem (and the thing which put me off tackling this on the current
>>> windows installer) is that there are so many ways that a use could have
>>> already set up their httpd.conf (with regard to global and vhost
>>> configurations, whether httpd.conf does all the config, or there are
>>>
13 matches
Mail list logo
