|The stupid question is the question not asked|
Module::Starter (or ::PBP) and Module::Build -- how do I configure the License and Copyright?by Cuhulain (Beadle)
|on Feb 07, 2010 at 16:56 UTC||Need Help??|
Cuhulain has asked for the
wisdom of the Perl Monks concerning the following question:
Module::Starter::Simple.pm has a subroutine _get_licenses_mapping that lets the module developer select from perl, mit, bsd, add other license text.
How can I plugin my own license and copyright text (tailored to my employers standard commercial wording)? I don't want to edit Module::Starter::Simple.pm directly. (That way would be easy, but surely is heretical.)
I've struggled thru some postings here on plugins and (brian d foy's posting on) the template toolkit. brian's discussion seemed to use Make, and I cannot see if it will work with Build, which I prefer. Much of this material is very new and I do not understand the true path to enlightment.
I am a recent convert to module-starter and Module::Build, and (very recently) to OO Perl. So, if Monks recommend I try sub-classing methods like _get_licenses_mapping, I'd barely know where to start. I have just successfully applied Test::Perl::Critic (to brutal severity), Test::Kwalitee, and Test::MockObject. These are elements of a very impressive toolkit.
But I need to find a way to tailor the module framework to suit my company and project before trying to persuade my colleagues to adopt these brilliant development tools.
The default POD from Module::Starter is not compliant with default perlcritic policies. I've had to manually create the missing POD sections in my module. To fix this, should I switch to Module::Starter::PBP for future module creation in gvim? I appreciate that it is new so may have bugs -- one posting discussed a possible bug in handling spaces in pathnames.