Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

acme (189)

acme
  (email not shown publicly)
http://www.astray.com/

Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Journal of acme (189)

Thursday July 11, 2002
03:21 PM

And another thing...

[ #6289 ]

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 /^[U-Z]/. I'm sure I'll find some more as I go along... ;-)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Okay, maybe we do need a guide of how to write a module properly so it can be automatically installed.

    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?

    • By default don't ask questions? Not very userfriendly. What should we do about optional features?
    • time out after a few seconds of inactivitly (easy to implement for all concerned, but a pain in the rear if I'm not watching my c
    • Well, I'm not going to try and change the world this week. I appreciate that it's not all as simple as it first seems, but what I'm going to concentrate on is getting CPAN in Gentoo. I already have a couple of workarounds and dependency additions etc., so I'm going to hack and slash until it all just works ;-)

      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
    • Interactive modules are a pain. But what do we do about it? By default don't ask questions? Not very userfriendly. What should we do about optional features?

      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.

  • I know when I have installed apache I have been able to avoid interaction with the make / install process, even when integrating SSL, Perl, etc.

    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;