You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Stas Bekman <st...@stason.org> on 2002/11/18 18:45:46 UTC
Re: cvs commit: httpd-apreq Makefile.PL
joes@apache.org wrote:
> joes 2002/11/17 15:18:04
>
> Modified: . Makefile.PL
> Log:
> Base libapreq-1.x tests on Apache::test, not Apache::Test (which seems to be for testing 2.x).
Apache::Test is designed to work with Apache 1.3 and 2.0. Meaning that
you can use the same tests suite for both Apache::Request versions. So
using the old framework might be not as good as the new one...
The only problem with automatic testing is that those who test don't
have Apache::Test installed.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: cvs commit: httpd-apreq Makefile.PL
Posted by Stas Bekman <st...@stason.org>.
Joe Schaefer wrote:
> Stas Bekman <st...@stason.org> writes:
>
>
>>Joe Schaefer wrote:
>
>
> [...]
>
>
>>>I agree, but it was simple enough to just move the modperl-1
>>>tests over. I had some trouble getting the Apache::Tests to
>>>run on my box, so I just copied over the tests from modperl-1.
>>>( Apache::Test kept reusing my modperl-2 test settings in
>>>Apache::BuildConfig. I couldn't figure out how to get around this. )
>>
>>You could have asked at the httpd-test mailing list. I believe in the
>>long run it's better to rely on something that works with both
>>versions. This gives us a better code reuse.
>
>
> Yes, in the non-short run. However, right now my immediate
> concern is to put together a 1.1 release candidate that
>
> 1) has a functional test suite
> 2) includes support for OS X.
> 3) has no support for modperl-2, yet.
>
> I'd like to have that ready this weekend, so I can notify the
> modperl lists and macosx lists. Once we get the green light
> from some users/testers, we can tag & roll a 1.1 release.
>
> After that, I'm all for moving efforts to including modperl-2
> support, including replacing Apache::test with Apache::Test.
Sounds good to me.
>>Apache::Test comes with 2.0 and eventually it'll be distributed
>>separately. So what we will do is simply make a dependancy rule in
>>Makefile.PL and this will force the testers to install Apache::Test on
>>their machine. I guess we should do this right now.
>
>
> No, I'd prefer to *not* do that until *after* a 1.1 release.
Certainly. As meant that this dependency will be a goood idea when
Apache::Test will be released
separately on CPAN.
--
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: cvs commit: httpd-apreq Makefile.PL
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Stas Bekman <st...@stason.org> writes:
> Joe Schaefer wrote:
[...]
> > I agree, but it was simple enough to just move the modperl-1
> > tests over. I had some trouble getting the Apache::Tests to
> > run on my box, so I just copied over the tests from modperl-1.
> > ( Apache::Test kept reusing my modperl-2 test settings in
> > Apache::BuildConfig. I couldn't figure out how to get around this. )
>
> You could have asked at the httpd-test mailing list. I believe in the
> long run it's better to rely on something that works with both
> versions. This gives us a better code reuse.
Yes, in the non-short run. However, right now my immediate
concern is to put together a 1.1 release candidate that
1) has a functional test suite
2) includes support for OS X.
3) has no support for modperl-2, yet.
I'd like to have that ready this weekend, so I can notify the
modperl lists and macosx lists. Once we get the green light
from some users/testers, we can tag & roll a 1.1 release.
After that, I'm all for moving efforts to including modperl-2
support, including replacing Apache::test with Apache::Test.
[...]
> Apache::Test comes with 2.0 and eventually it'll be distributed
> separately. So what we will do is simply make a dependancy rule in
> Makefile.PL and this will force the testers to install Apache::Test on
> their machine. I guess we should do this right now.
No, I'd prefer to *not* do that until *after* a 1.1 release.
--
Joe Schaefer
Re: cvs commit: httpd-apreq Makefile.PL
Posted by Stas Bekman <st...@stason.org>.
Joe Schaefer wrote:
> Stas Bekman <st...@stason.org> writes:
>
>
>>Apache::Test is designed to work with Apache 1.3 and 2.0. Meaning that
>>you can use the same tests suite for both Apache::Request versions. So
>>using the old framework might be not as good as the new one...
>
>
> I agree, but it was simple enough to just move the modperl-1
> tests over. I had some trouble getting the Apache::Tests to
> run on my box, so I just copied over the tests from modperl-1.
> ( Apache::Test kept reusing my modperl-2 test settings in
> Apache::BuildConfig. I couldn't figure out how to get around this. )
You could have asked at the httpd-test mailing list. I believe in the
long run it's better to rely on something that works with both versions.
This gives us a better code reuse.
>>The only problem with automatic testing is that those who test don't
>>have Apache::Test installed.
>
>
> It does simplify the module dependencies though,
> since Apache::test comes with modperl-1.x.
Apache::Test comes with 2.0 and eventually it'll be distributed
separately. So what we will do is simply make a dependancy rule in
Makefile.PL and this will force the testers to install Apache::Test on
their machine. I guess we should do this right now.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: cvs commit: httpd-apreq Makefile.PL
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Stas Bekman <st...@stason.org> writes:
> Apache::Test is designed to work with Apache 1.3 and 2.0. Meaning that
> you can use the same tests suite for both Apache::Request versions. So
> using the old framework might be not as good as the new one...
I agree, but it was simple enough to just move the modperl-1
tests over. I had some trouble getting the Apache::Tests to
run on my box, so I just copied over the tests from modperl-1.
( Apache::Test kept reusing my modperl-2 test settings in
Apache::BuildConfig. I couldn't figure out how to get around this. )
> The only problem with automatic testing is that those who test don't
> have Apache::Test installed.
It does simplify the module dependencies though,
since Apache::test comes with modperl-1.x.
--
Joe Schaefer