David Golden wrote:
On Thu, Feb 28, 2008 at 11:47 PM, Christopher J. Madsen <[EMAIL PROTECTED]>
wrote:
As I was about to check in these changes, I realized that's the wrong
way to do it. I want these features in all my modules, and I don't want
to have to copy & paste them into My_Build subclasses. And I'll bet
other people would find it useful.
In my distributions, I have an inc/ directory and put my custom
Module::Build subclass there. In generally, I try to have all custom
actions -- such as filling in the VERSION section of documentation --
happen during the packaging of the distribution, rather than at
installation. That way, end users don't need my custom subclass --
for example if they don't have Pod::WikiDoc, it doesn't even get
loaded.
I like this approach because it doesn't impose a configure-time
external dependency for what is really a way of making things easier
for me as an author.
I added a similar scheme to Perl::Critic. We've got an "inc" directory in which we put a
copy of Devel::CheckOS and our own build utility module. (The module is unfortunately not a M::B
subclass because the distro also supports using EU::MM.) But the "inc" directory scheme
works well. No muss, no fuss, for either developers or users.
