@@ -63,4 +63,6 @@ Or if you want to submit to CPAN you will use the ''.tar.gz'' file generated by
All of the files ''dzil'' generates are put in a target directory and none of your source files are changed by ''dzil''. This allows you to keep generated files strictly separate from the files you edit. It also enables consistent builds. ''dzil build'' will allways generate all boilerplate and keep the distribution of your package consistent.
''Dist::Zilla'' supports both ''Module::Build'' and ''ExtUtils::MakeMaker'' as backends. So you continue to profit from the work that went into ''Module::Build'' and avoid the burden of updating all the boilerplate.
''Dist::Zilla'' supports both ''Module::Build'' and ''ExtUtils::MakeMaker'' as backends. So you continue to profit from the work that went into them and avoid the burden of updating all the boilerplate. It also allows you switch between ''ExtUtils::MakeMaker'' and ''Module::Build'' by substituting one plugin for the other. See, you can have it both ways :-)
For most typical projects ''Dist::Zilla'' is the ideal package maintenance tool. Once your project becomes more complex you may encounter some limitations. You can then either dig into the internals of ''ExtUtils::MakeMaker'' or write your own ''Dist::Zilla::Plugin::'. Writing your own plugin may well turn out to be the better choice.
