home.social

#dzil — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dzil, aggregated by home.social.

  1. We just got bitten at work by what we think is an incompatible change in the Dist::Zilla ecosystem. I remember seeing somewhere in the dzil doco that it was unstable and liable to incompatible changes at any time, which is one of the reasons why I have for years recommended that no-one ever use it.

  2. @smonff And #DZil ain’t that steep a learning curve. The basics are literally *easier* than authoring a Makefile.PL or Build.PL

    And metacpan.org/pod/Dist::Zilla:: exists

    #DistZilla #Perl

  3. @rrwo It *does* have everything #DZil built! In fact, I specifically crafted my dist.ini with that aim.

    The `build/main` branch has everything generated from main: codeberg.org/mjgardner/perl-Lo

    And the `build/release` branch has everything generated for #CPAN releases: codeberg.org/mjgardner/perl-Lo

    And the "How to contribute” documentation tells you how to do both: metacpan.org/dist/Log-Any-Adap

    Suggestions and PRs welcome!

    * codeberg.org/mjgardner/perl-Lo
    * codeberg.org/mjgardner/perl-Lo

    #Perl

  4. Sorry to all the #dzil haters, but in the end I'm going back to Dist::Zilla for this and my other #Perl #CPAN distributions. I tried the alternatives, but they all failed me for one reason or another.

    And in the end, it's just hard to argue with a negative line count delta.

    The good news is that I've got it configured to maintain build/main and build/release branches that one can fork and contribute to without having to install all my dependencies.

    I think I feel another blog post coming on.

  5. I've released a new version of Dist-Zilla-Plugin-UsefulReadme to #CPAN.

    This is a #perl #dzil plugin for generating a README with just the useful bits of the module POD.

    This latest version adds a minor option to disable adding prerequisites (mainly for bootstrapping itself) and tweaks some tests.

    metacpan.org/release/RRWO/Dist

  6. @jochie #Perl POD is static at rest by nature, so there’s no built-in way to bake a program/topic in there.

    However, @rjbsmetacpan.org/pod/Dist::Zilla is a great “maximum overkill” system for automating boilerplate POD (via metacpan.org/pod/Dist::Zilla::), tests, version control operations, deployments, etc.

    There are other tools on #CPAN to do only what you want and stop there, but #dzil can grow with you.

  7. @ChristosArgyrop #dzil is pretty awesome for scaling up all the boilerplate operations of maintaining and releasing multiple #CPAN module distributions. Many thanks to @rjbs

  8. Dear @Perl folks that use Dist::Zilla. I'm trying to release a new version of Validation::Class but I'm stuck with dzil release. All tests pass, files are modified but for some reason the modifications aren't committed to Git?

    To clarify, my Git index is clean before running the release command.

    I've got no clue on how to proceed here as I barely know how Dist::Zilla works.

    github.com/Htbaa/Validation-Cl

  9. @ovid Speaking for myself when publishing my first CPAN dist: #dzil was easiest! It was the only thing I saw that matched my mental model. 🤷

  10. I feel sorry for any brand-new developer who wants to publish their first module to the .

    I now use . I can't imagine that's useful for a new developer.

    What's the easiest way for a new developer to learn to publish something to the CPAN?

  11. @DrHyde @Perl It’s understandable when you consider @rjbs invented it to maintain his 200+ #CPAN dists. And it’s possible to enable folks to successfully contribute to #dzil projects without making them use it. Unfortunately, that’s not configured by default.

  12. @EndlessMason @davehodg #dzil also includes a plug-in to automatically rewrite tests in `xt` to skip unless the appropriate environment variable is set, so you don’t have to remember to write that in your test scripts yourself metacpan.org/pod/Dist::Zilla:: #Perl