Re^6: What do I use to release a module to CPAN for the first time?

I disagree.

Many Dist::Zilla project only have a dist.int and no Makefile.PL, so you will need the whole bloody suite to get started anyway.

However I applaud people using something to make their dist meet every standard and make their own lives easier to maintain and distribute their modules, IMHO Dist::Zilla is a (very) bad part of the toolchain to draw in fresh blood or make it easier for others (not using it) to submit changes.

I have not seen a project that uses Dist::Zilla where I could get away without Dist::Zilla installed

Enjoy, Have FUN! H.Merijn

Comment on Re^6: What do I use to release a module to CPAN for the first time?

Replies are listed 'Best First'.
Re^7: What do I use to release a module to CPAN for the first time? by tobyink (Canon) on Oct 12, 2020 at 08:43 UTC
But to write a patch, test it, and submit it back to the maintainer, why would you need Makefile.PL? (I'm assuming a pure Perl distribution here; no XS.) toby döt ink	[reply]
Re^8: What do I use to release a module to CPAN for the first time? by Tux (Canon) on Oct 12, 2020 at 09:02 UTC
Even if I know most about testing and I know about `prove` and `yath`, my usual start is always the same: Get the dist `git clone` / `cpan + get` / get the tgz Prepare `$ cd Module-dir` `$ perl Makefile.PL` If it complains about no Makefile.PL, curse loudly, check if there is a Build.PL `$ perl Build.PL` If there is no Build.PL either, curse even louder and ask myself the question if applying my patch is worth the trouble. If not, just give up. Test `$ make test` If it complains about missing Makefile, curse again and try Build.PL `$ perl Build test` If I really cared enough, and installed enough of dzil `$ dzil test` If that still complains about yet another missing plugin, give up and remove the dist dir: My time is valuable too. Hack If this module now passes all tests, check if my change still applies. (It might have been fixed in the git repo already). Otherwise, make the change, make a test case, update ChangeLog (or any other legal name) and submit a PR. Even as a seasoned perl programmer with enough knowledge to get the ball rolling, I see plenty of decision points where I would decide to leave the annoyance/bug to what it is and maybe just add an issue, which in most cases is much easier than going through the installation of dependencies I won't need for anything but this single module. Enjoy, Have FUN! H.Merijn	[reply] [d/l] [select]
Re^9: What do I use to release a module to CPAN for the first time? by perlancar (Hermit) on Oct 12, 2020 at 14:05 UTC
Even if I know most about testing and I know about prove and yath, my usual start is always the same: Which begs the question: if you know prove and "prove -l" works (it is most of the time), why go the hard way?	[reply]
Re^8: What do I use to release a module to CPAN for the first time? by Corion (Patriarch) on Oct 12, 2020 at 08:44 UTC
At least for installing the prerequisites, and if the author uses Pod::Weaver, even a docpatch can't be applied by the module maintainer well.	[reply]
Re^7: What do I use to release a module to CPAN for the first time? by Anonymous Monk on Oct 14, 2020 at 14:36 UTC
Then I suppose you have not seen any of my projects, or any using Dist::Milla, or David Golden's bundle, etc. -Dan	[reply]
Re^8: What do I use to release a module to CPAN for the first time? by Tux (Canon) on Oct 14, 2020 at 15:13 UTC
Then your projects (and David's) most likely (also) have a proper Makefile.PL. In that case we (non Dist::Zilla users) won't even notice. I'll be a sport and not alter my original response, which states "Many" in the first sentence and lacks the addidion of "that not have a Makefile.PL" in the last sentence. Enjoy, Have FUN! H.Merijn	[reply]