I once spend an hour or so determining what I want as a boilerplate. Which is just a few files: Makefile.PL (tailered to what I want), MANIFEST, MANIFEST.SKIP (for .git, .gitignore, and MANIFEST.SKIP itself), Changes (with just one line), README (empty), t/000_load.t (just tests whether the module loads), t/001_pod.t (checks for pod compliance), a skeleton .pm file, and a .gitignore file. Then I spend another hour writing a simple Perl script which takes the name of the module-to-be as argument, and uses that to create the mentioned files, in a appropriate directory. It also sets up the directory as a git repository, and does an initial checkin of the files created.

Two hours very well spend. Sure, I end up with something that only works for me, but who cares? Now I can just type "cpan-start My::Module", and two seconds later I can start actual coding, instead of manually editing whatever a more general module or script has produced. If my preferences change over time, I just modify the script (and since it's just my script, I don't have to care about backwards compatibility, or have it do something something else way want). If I ever were to create XS modules on a more regular basis, I'd modify the script to take an -xs option, and create a different skeleton. Now I create XS modules so infrequently, I just use h2xs and do some manual editing afterwards.

My advice: figure out what *you* want, and write a script that just does that. Takes far less time than trying to find out whether someone has written and published something that does exactly what you want.

In reply to Re: Alternatives to Module::Starter by JavaFan
in thread Alternatives to Module::Starter by Xiong

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.