in reply to Re: What to tell Module::Build, and where?
in thread What to tell Module::Build, and where?

I agree, though usually keep my own perl in either ~/opt, or else maybe /opt. This way, you can keep all of it under the same tree (which makes an uninstall very easy (i.e. rm -fr ~/opt/perl-5.10.0), if that's ever necessary).

I've never used Perl::Install. I just read the build instructions that come with Perl and go to it.

  • Comment on Re^2: What to tell Module::Build, and where?

Replies are listed 'Best First'.
Re^3: What to tell Module::Build, and where?
by dragonchild (Archbishop) on Apr 21, 2008 at 09:26 UTC
    I would normally agree, but I found myself having to install Perl over and over as part of a deployment process. So, I threw this together as a first-pass CPAN-ization of my scripts.

    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?