I say don't support them, to an extent; you don't want to force everyone to
have the latest and greatest. A few older versions should work; maybe back
to 1.3.12 or 15.
Anyone who runs a flawed product is asking for trouble, look at all the
NT/2K IIS machines :)
A lot of hosting companies are still running fairly old versions of Apache,
but this is due to the fact they have poor upgrade capabilities because of
their 99.xxx% uptime guarantees. Plus their techs seem to be scared of new
things??
-Chris
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Jani Taskinen
Sent: Monday, 25 June, 2001 3:17 PM
To: Wilfredo Sanchez
Cc: [EMAIL PROTECTED]
Subject: [PHP-DEV] Support Apache 1.3.6 or not?
On Mon, 25 Jun 2001, Wilfredo Sanchez wrote:
>
>On Monday, June 25, 2001, at 06:58 AM, Jani Taskinen wrote:
>
>> This happens because of your patch. What is the use of -S anyway? :)
>> Could you please check this out?
>
> -S sets the value of an apache configuration variable used by apxs.
>It may have been added after 1.3.6, which would explain why it craps out
>in this case. If 1.3.6 is important, we may have to back out that part
>of the patch, but then installing into a package root won't work any
>more.
I forgot to Cc: this to the mailing list. Anyway, IMO we shouldn't
bother supporting that old versions of Apache. It's already in version
1.3.20 and there have been a lot security patches since 1.3.6, IIRC.
So there should be more reasons to update than not to.
But I'd like to hear other opinions too before doing anything about this.
--Jani
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
