Front page | perl.perl5.porters |
Postings from October 2009
On Tue, Aug 25, 2009 at 09:33:22AM -0400, Curtis Jewell via RT wrote:
> I wouldn't plonk him quite so fast, although I would have said "That's
> not neccessarily true - you should see some of the multiple-machine
> installs I've had to do!" instead of what he DID say.
>
> The workaround is itself less correct than it could be, as it should be
> testing $ENV{PERL_MM_USE_DEFAULT} as well, which is what is usually set
> when people do not want interactive installations, but aren't
> neccessarily a CPAN smoker. Check for that, as well, and I would think
> 99% of complaints on this issue would disappear.
I decided to invent a new name unilaterally.
PERL_MM_NONINTERACTIVE
If true, indicates that makemake'd modules should not be interactive.
I recommend to test for it in addition to $ENV{PERL_MM_USE_DEFAULT} in
makemaker itself, and document it for module writers. Likewise for
Module::Builder?
I think
a) AUTOMATED_TESTING should be better confined to one particular
situation - smoke tests. (There may be need to distinguish it
from other types of non-interactive testing.)
b) PERL_MM_USE_DEFAULT is already documented, and its design goal is
too narrow;
c) Due to chicken and egg, something should come first (usage in
modules, usage in MakeMaker, documentation?). I did in
Term::ReadLine::Perl 1.0303.
Yours,
Ilya
Thread Next