On Jan 29, 2008 11:15 AM, Ian Malpass <[EMAIL PROTECTED]> wrote: > Mm. I'd rather not have to embed Pod::Snippets in my distribution (that > seems excessive somehow) or make it a build prereq. Test::Pod::Snippets > does what I need, I just want it to do it at a particular time. > Subclassing seems to be the way to go. > > You might want to look at the approach I use for documentation for many of my distributions. I write my documentation in "WikiDoc" format in the .pm file and then have a custom Module::Build class use Pod::WikiDoc to extract it and generate .pod files that get packaged in the distribution. So while *I* need to have Pod::WikiDoc installed to make the distribution tarball, the end users don't -- they just have the .pod files.
To see how it works, look at the latest CPAN-Reporter -- the custom M::B class is in the inc/ directory and the Build.PL file uses that only if Pod::WikiDoc is installed. (And anyone interested in Pod::WikiDoc -- see my YAPC lightning talk: http://dagolden.com/files/pod-wikidoc.pdf ) Regards, David
