Re^2: Interactivity in tests

Thanks! I came across ExtUtils::MakeMaker::prompt when looking for answers to this question prior to posting (should have mentioned that). Correct me if I'm wrong, but I was under the impression that using E::MM::prompt means that

a.) Anyone installing the module via Module::Build would not be prompted?

b.) Everyone installing the module interactively (via Makefile.PL) would be prompted?

I don't want either of these, I like to provide both a Build.PL and Makefile.PL so people have the choice of install system to use. And I also don't want to prompt every user for this information, I just want to tell the user "you can test this against against a live service if you want, and if you tell me to do so I'll prompt you for the information that's required".

Not saying your suggestion is a bad one, but if both of these assumptions are true it's just not the right fit for me.

All dogma is stupid.

Comment on Re^2: Interactivity in tests - done correctly? Download Code

Replies are listed 'Best First'.
Re^3: Interactivity in tests - done correctly? by Anonymous Monk on Jan 23, 2009 at 07:31 UTC
ExtUtils::MakeMaker::prompt is the de-facto standard for prompt and Module::Build follows the convention. http://search.cpan.org/dist/Module-Build/lib/Module/Build/API.pod#prompt. If you want it to be optional, you can always `perl ....PL --promptme if( $promptme ){ ...prompt(... } # OR if( $ENV{prompt_me_big_boy} ){ ...prompt(... }` [download]	[reply] [d/l]