Hmmm, I'm obviously also not alone in being with your boss on this one.

I've never used Module::Starter - plain, good old h2xs has always fitted the bill perfectly well for me. With this make & make test are both dependencies of make install, so once the makefile has been generated, there's only ever one command to recall and re-run - and unless it's been Windoze-based perl/make session to a networked filesystem, any extra time spent is negligible ... to the point of being infinitesimally small.

The one thing I notice you haven't mentioned is the notion of unit test - the skeleton for which comes for free with h2xs (and possibly/probably Module::Starter) - and (as mentioned above) gets executed prior to installation - thus providing a far greater degree of confidence in the installed module (assuming adequate test script(s) coverage).

WRT ...adding another module would mean editing a MANIFEST file each time., you self-evidently haven't heard of make manifest (having first tidied up the development area).

A user level that continues to overstate my experience :-))

In reply to Re: modular app development - where do your modules live? by Bloodnok
in thread modular app development - where do your modules live? by metaperl

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.