You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2002/04/08 17:57:10 UTC
shortening problem diagnosis phase in modperl list threads
David Harris has suggested to log all the build errors/warnings into a
file BUILD_ERRORS, so if users have a problem the SUPPORT doc will first
ask them to check if they have any errors in this file. This should
somewhat shorten the number of emails before a user in trouble realizes
that she needs to check whether some errors/warnings went unnoticed
using this file.
This becomes especially important if we decide not to use the colored
output to make errors and warnings to stand out.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: cutting on build's process noise
Posted by Doug MacEachern <do...@covalent.net>.
On Tue, 9 Apr 2002, Stas Bekman wrote:
> and if MP_TEST_TRACE is not defined, should it inherit MP_BUILD_TRACE or
> not?
no, should stay the default.
> and an equivalent APACHE_BUILD_TRACE?
no, i meant APACHE_TEST_TRACE to be supported in Apache::TestTrace, not
specific to mod_perl.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: cutting on build's process noise
Posted by Stas Bekman <st...@stason.org>.
Doug MacEachern wrote:
> On Tue, 9 Apr 2002, Stas Bekman wrote:
>
>
>>As we move to use Apache::TestTrace for controlled output,
>>I propose a new build flag MP_NOISE flag equivalent to t/TEST's:
>> -trace=T change tracing default to: warning, notice, info,
>>debug, ...
>
>
> +1 or:
> MP_TRACE - what it already is
> MP_BUILD_TRACE - what you're saying MP_NOISE would be
> MP_TEST_TRACE - passed to t/TEST -trace $MP_TEST_TRACE
>
> so one could get a noisy build but less noisy test, etc.
and if MP_TEST_TRACE is not defined, should it inherit MP_BUILD_TRACE or
not?
>>So by default we will have this set to 'warning' and let user override
>>these.
>
>
> sounds good.
>
>
>>Or would be an env var a better solution? Or both?
>
>
> both would be useful. APACHE_TEST_TRACE
and an equivalent APACHE_BUILD_TRACE?
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: cutting on build's process noise
Posted by Doug MacEachern <do...@covalent.net>.
On Tue, 9 Apr 2002, Stas Bekman wrote:
> As we move to use Apache::TestTrace for controlled output,
> I propose a new build flag MP_NOISE flag equivalent to t/TEST's:
> -trace=T change tracing default to: warning, notice, info,
> debug, ...
+1 or:
MP_TRACE - what it already is
MP_BUILD_TRACE - what you're saying MP_NOISE would be
MP_TEST_TRACE - passed to t/TEST -trace $MP_TEST_TRACE
so one could get a noisy build but less noisy test, etc.
> So by default we will have this set to 'warning' and let user override
> these.
sounds good.
> Or would be an env var a better solution? Or both?
both would be useful. APACHE_TEST_TRACE
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
cutting on build's process noise
Posted by Stas Bekman <st...@stason.org>.
As we move to use Apache::TestTrace for controlled output,
I propose a new build flag MP_NOISE flag equivalent to t/TEST's:
-trace=T change tracing default to: warning, notice, info,
debug, ...
though MP_TRACE is taken already.
So by default we will have this set to 'warning' and let user override
these.
Or would be an env var a better solution? Or both?
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: shortening problem diagnosis phase in modperl list threads
Posted by Doug MacEachern <do...@covalent.net>.
On Mon, 8 Apr 2002, Stas Bekman wrote:
> David Harris has suggested to log all the build errors/warnings into a
> file BUILD_ERRORS, so if users have a problem the SUPPORT doc will first
> ask them to check if they have any errors in this file. This should
> somewhat shorten the number of emails before a user in trouble realizes
> that she needs to check whether some errors/warnings went unnoticed
> using this file.
not sure how you'd go about this, capturing warnings/errors from the
compiler, MakeMaker, etc. we only have control over what the modperl
Makefile.PL's warn/error.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org