This sounds like it would make life a lot easier for automation. I hacked together a build system a few weeks which used CPAN.pm to install modules which were specified in an xml file that had module name, author, and version. I hit several roadblocks when working with Module::Build based modules because I needed to use PREFIX functionality.

I ended up having my build system bootstrap a fresh perl installation, source a new profile, install a CPAN Config.pm, then prompt the user to re-run the build under the newly installed perl. It solved several problems with regards to the Module::Build issues, but had the downside of taking a long time to setup from scratch. On the plus side, to upgrade to a new module, all I had to do was update the version in the xml file, and run 'build --module module_name'. No modules to download and add to the source repository.

Here's a snippet of the build config file:

<cpan>
    <module name="Apache2::AuthCookie" path="M/MS/MSCHOUT/" version="3
+.08"/>
    <module name="CGI" path="L/LD/LDS/" version="3.08"/>
    <module name="BerkeleyDB" path="P/PM/PMQS/" version="0.26"/>
</cpan>

[download]

In reply to Re: Module::Build users -- please use the "traditional" create_makefile_pl option by redhotpenguin
in thread Module::Build users -- please use the "traditional" create_makefile_pl option by perrin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.