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.
I do a form of this already because I write my documentation using Pod::WikiDoc. 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. When I create a new distribution, I just "cp -a" the inc/ directory and a Build.PL template and I'm on my way. For an example of my Build.PL and inc, look at http://search.cpan.org/dist/CPAN-Reporter/ Regards, David
