Module::Build, like ExtUtils::MakeMaker and Module::Install, were written for a world where you don't have configure-time dependencies. Thus the trend to large and involved single packages with everything included, just as things like CGI.pm were before it in the days when we didn't have any dependencies at all.
Once a CPAN with configure_requires becomes the toolchain back-compatibility target the age of the large self-contained build system will come to an end, and you'll see a trend to more diverse, dynamic and componentised build systems. This is largely inevitable, and Leon just represents the leading edge of this change. Adam K On 8 March 2011 06:34, John M. Gamble <jgam...@ripco.com> wrote: > On 3/7/2011 6:06 AM, Leon Timmermans wrote: >> >> On Sat, Mar 5, 2011 at 9:43 PM, David Golden<xda...@gmail.com> wrote: >>> >>> Since then, my own use of Module::Build has declined, as much of my >>> need for it as an author has been replaced by Dist::Zilla toolkit. At >>> the same time, I've taken on additional responsibilities with P5P, >>> CPAN PAUSE administration, and other parts of the toolchain. >>> >>> Therefore, with the release of 0.3800, I am retiring as Module::Build >>> release manager. I will continue to contribute occasional patches, >>> particularly relating to any bugs uncovered in the new CPAN Meta Spec >>> v2 support added in 0.3800, but do not plan to release any more >>> tarballs to CPAN, short of a major flaw in 0.3800 requiring an >>> emergency fix. >>> >>> I encourage interested parties to speak up and volunteer to take on >>> the release manager role. >> >> I'm not particularly interested in improving Module::Build. I am very >> much interested in cannibalizing pieces of its code to make them >> reusable for the second generation of Build.PL builders, which will >> hopefully obsolete Module::Build in the future. Depending on your >> point of view this would make me either the worst or best possible >> candidate to manage Module::Build. In either case I do not think I >> would be doing it for more than just a handful of releases though. >> >> Leon >> > > Well ... this raises a question. Whither Module::Build? > > Is its future simply to be the precursor to Dist::Zilla? Or to be wrapped > up as a Dist::Zilla::Simple? > > I'm on this list because once I found out about Module::Build, I transferred > my modules over to it as fast as my little fingers could edit them, and I > wanted to learn more as it developed. I like it, it was and is a much easier > system to use, and if it doesn't have an independent future I'd like to see > it become a bridge to an even easier system, not simply broken apart. > > -john > >
