Things I don't like: CPAN modules which depend on modules which aren't actually on the CPAN, modules that fail their own tests, modules without a Makefile.PL, modules that don't generate a Makefile, modules which compile C code during 'perl Markfile.PL', modules which require sane user input for configuration (ie not just return for every question). And that's just for starters. I've only done module distributions with names that match
Ah, maybe we need a guide (Score:2)
I have an install script that installs all them modules I need at work and I do run into the same kind of problems.
Interactive modules are a pain. But what do we do about it?
Re:Ah, maybe we need a guide (Score:2)
After I've done that, we can go back and decide what would have made things easier for me and what the best solution might be. Of course, most talk about CPAN is just that - we need to get the module
Re:Ah, maybe we need a guide (Score:1)
Why, command line options to "perl Makefile.PL", of course. Of course? Eh, the concept is there. I don't know how extensible it is, to use your own command line options.
if it works for apache... (Score:1)
some kind of option to use-default, use-env or use-file instead of interactions would be very useful. Does ABW's tool that installs TT do something along those lines?
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;