Re: separating Module::Build's dev bits
[email protected] (Eric Wilhelm)
| Newsgroups | perl.module.build |
|---|---|
| Message-ID | <[email protected]> |
# from Christopher J. Madsen
# on Friday 02 October 2009 14:20:
>I think MB ought to be split up into the "build/test/install module"
>part and the "tools for distribution authors" part. MakeMaker
> combined the two, and MB followed suit, but I don't think it was a
> good idea.
It has the benefit of greatly democratizing the development process
("everyone gets the full kit"), but yes, at the cost of constraining
the usage to fit the destination.
> It sounds like that's what you're talking about.
Well, I've been thinking that it's related to plugins. That is, some
plugins should be allowed to be missing so long as the methods they
hook/provide/affect are never called. But of course that means you
would have to register the plugins in your Build.PL or something so
that the loader still knows what they do even in their absence. Maybe
a directory full of declarative bits or something.
--Eric
--
software: a hypothetical exercise which happens to compile.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------