[MSCHWERN - Wed Jun 29 16:00:55 2005]:
Show quoted text> [KANE - Thu Nov 11 10:31:30 2004]:
> > > local $ENV{PERL_MM_USE_DEFAULT} = 1 unless $run_verbose;
>
> I just noticed this. I'm not really sure what verbosity has to do with
> this.
'verbose' is the terminology used here meaning 'with output to the screen'. If you have
verbose turned off *and* allow_build_interactivity disabled, then we'll set
PERL_MM_USE_DEFAULT so that in most cases, no interactive install will happen.
Show quoted text> Running verbosely doesn't change the automated nature of running
> Makefile.PL, the user still doesn't get prompted, Makefile.PL is not
> being run interctively.
Show quoted text> I noticed this while installing Data::UUID which will only prompt if
> PERL_MM_USE_DEFAULT is set.
You mean *not* set.
Show quoted text> CPANPLUS hung running its Makefile.PL
> because I have verbose turned on. I was not offered any prompt.
Actually, it didnt *hang* it merely didn't show you the output from Data::UUID's makefile.pls
print statement. A simple buffering issue.
I can fix it with a '-Mfoo' where foo.pm holds BEGIN { $|++ }.
So, i've added a .pm in the CPANPLUS namespace that does exactly that, which will
be included before any makefile.pl is run using -M.
Patch is applied as change 12121
Show quoted text> Unless I'm missing something, the correct behavior should be to always
> set PERL_MM_USE_DEFAULT regardless of verbosity.
Definately not. When people want to answer question interactively, they should
be able to do so.