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)? /

From that, I think it's clear that I can already select "perl", for example, and standard text is plugged in. But that standard text is not tailored to my employers standard commercial wording.

It looks like Module::Starter produces a template that falls far short of perlcritic standards, but a Build program that works despite pathnames embedding spaces. In contrast, Module::Starter::PBP produces a template that almost meets perlcritic standards, but a Build program that fails if pathnames embed spaces.

The clumsy compromise seems to be to use Module::Starter::PBP once only to generate a template, then fix that template's few bugs and keep it, then always use Module::Starter to generate new frameworks and Build programs, but overwrite its template with the saved perlcritic compliant one (as a Vim plugin, say).

Wouldn't it be nice if the few critical rough corners on Module::Starter::PBP were smoothed off . . .

Or can any Monk recommend a better way towards a really classy, standardised, consistently-tailored module-production mechanism?