In article <[EMAIL PROTECTED]>, Andy Lester <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 24, 2005 at 07:46:38AM -0500, Ken Williams ([EMAIL PROTECTED]) > wrote: > > Personally I still don't think that's the best place for it. Why make > > all the people who *download* your module check something that should > > be checked at "make dist" time? > > Did people not like the idea of putting these checks as plugins into > > Module::Release? > We saw putting it in Module::Starter as a place to start. JFDI and > all that. Well, each module making tool is going to have to tell someone what its boilerplate looks like. I think each module tool will have to have it's own boilerplate.t, so each tool might as well make its own. However, with the right interface, a Module::Release plugin could get that boilerplate.t from the module tool. :) -- brian d foy, [EMAIL PROTECTED]
