> Hi Geoff,
>Sorry for the delay - it's been a crazy two weeks ...
that's fine. it's good to have you back :)
> Anyway, you're right that this is fine now with 2.0.49 -
> thanks.
cool, thanks. I'll apply the patch as given, then we can all argue over how
exactly to use have_min_apache_ver
On Thu, 8 Apr 2004, Geoffrey Young wrote:
> hi all
>
> can somebody on win32 verify this patch for me? IIRC the
> required fix was committed in november, and 2.0.49 is the
> latest release that contains the fix, so all should be ok
> now.
>
> thanks
>
> --Geoff
Hi Geoff,
Sorry for the delay -
Geoffrey Young wrote:
At the moment the only idea I have is to have 2 different sets of APIs
which underneath will call the same core functions. e.g.:
skip_have_...
have_...
the only difference is that skip will also push the reason, and non-skip
won't. But may be there are better ideas.
I don't
> At the moment the only idea I have is to have 2 different sets of APIs
> which underneath will call the same core functions. e.g.:
>
> skip_have_...
> have_...
>
> the only difference is that skip will also push the reason, and non-skip
> won't. But may be there are better ideas.
I don't thin
Geoffrey Young wrote:
+use constant APACHE_2_0_49 => have_apache_version('2.0.49');
I think we need a separate API for this kind of things. The problem with
using
have_apache_version is that if you don't have it, it'll push the reason
into @skip list and if the test gets skipped it'll print that
>> +use constant APACHE_2_0_49 => have_apache_version('2.0.49');
>
>
> I think we need a separate API for this kind of things. The problem with
> using
> have_apache_version is that if you don't have it, it'll push the reason
> into @skip list and if the test gets skipped it'll print that reason
Geoffrey Young wrote:
hi all
can somebody on win32 verify this patch for me? IIRC the required fix was
committed in november, and 2.0.49 is the latest release that contains the
fix, so all should be ok now.
thanks
--Geoff
hi all
can somebody on win32 verify this patch for me? IIRC the required fix was
committed in november, and 2.0.49 is the latest release that contains the
fix, so all should be ok now.
thanks
--Geoff
Index: t/response/TestAPR/finfo.pm
