in reply to RFC: configure.pl

I really really really hate it when authors try that configure stuff. It should always be
  1. perl Makefile.PL
  2. make
  3. make test
  4. make install
As a cpantester, I really really really really hate it when authors throw me curves.

Now all authors have to remember is that Makefile.PL is a perl program and can do whatever you want it to do (interactively prompt or whatever).

Module::Build is a great potential contender for replacing MakeMaker.

I can live with the fact that Module-Build uses Build.PL, and I love the fact that it generates a perl program, but I hate that it still assumes *nix-isms (./Build don't work on windoze -- PATHEXT aside).

As a module author, I will only consider using Module::Build when it makes it into perl core, and is mature enough, which won't happen anytime soon (i just don't see it happening --- and I ain't including it in my distributions).


MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: RFC: configure.pl
by belg4mit (Prior) on Feb 13, 2003 at 13:54 UTC
    That's really not the point. If you note, it's intended for non-modules. And I had considered linking configure.pl to Makefile.PL, or otherwise invoking the former from the latter. Yes, Makefile.PL is a perl script (despite the odd choice of extension case). However, it also belongs to an arcane system that only a mother could love.

    --
    I'm not belgian but I play one on TV.