Dist::Zilla::PluginBundle::Author::BBYRD - DZIL Author Bundle for BBYRD


    ; Very similar to...
    ; Makefile.PL maker
    Dist::Zilla::MintingProfile::Author::BBYRD = profiles
    first_version = 0.90
    ; File modifiers
    config_plugin = @Author::BBYRD
    ; File pruners
    ; Extra file creation
    [ReadmeAnyFromPod / ReadmePodInRoot]    ; Pod README for Root (for GitHub, etc.)
    [ReadmeAnyFromPod / ReadmeTextInBuild]  ; Text README for Build
    [ReadmeAnyFromPod / ReadmeHTMLInBuild]  ; HTML README for Build (never POD, so it doesn't get installed)
    ; t/* tests
    ; POD tests
    ;[Test::PodSpelling]  ; Win32 install problems
    ; Other xt/* tests
    ;[MetaTests]  ; until Test::CPAN::Meta supports 2.0
    trailing_whitespace = 0
    ;[Test::Pod::LinkCheck]  ; Both of these are borked...  
    ;[Test::Pod::No404s]     ; ...I really need to create my own
    ; Prereqs
    minimum_perl = 5.10.1
    ; META maintenance
    directory = t
    directory = xt
    directory = examples
    directory = corpus
    meta_noindex = 1        ; respect prior no_index directives
    x_irc          = irc://
    bugtracker.web =
    ; Post-build plugins
    move = .gitignore
    move = README.pod
    ; Post-build Git plugins
    test_min_deps = 1
    branch = 
    release_branch = build/%b
    release_message = Release build of v%v (on %b)
    allow_dirty = dist.ini
    allow_dirty = .travis.yml
    allow_dirty = README.pod
    changelog =
    commit_msg = Release v%v
    push_to = origin master:master
    push_to = origin build/master:build/master
    metacpan = 1
    ; sanity deps
    ; authordep autovivification
    ; authordep indirect
    ; authordep multidimensional


I frelling hate these things, but several releases in, I found myself needing to keep my dist.ini stuff in sync, which requires a single module to bind them to.


I'm a strong believer in structured order in the chaos that is the CPAN namespace. There's enough cruft in CPAN, with all of the forked modules, legacy stuff that should have been removed 10 years ago, and confusion over which modules are available vs. which ones actually work. (Which all stem from the same base problem, so I'm almost repeating myself...)

Like I said, I hate writing these personalized modules on CPAN. I even bantered around the idea of using MetaCPAN's author JSON input to store the plugin data. However, keeping the Author plugins separated from the real PluginBundles is a step in the right direction. See KENTNL's comments on the Author namespace for more information.


This uses Dist::Zilla::Role::PluginBundle::Merged, so all of the plugins' arguments are available, using Merged's rules. Special care should be made with arguments that might not be unique with other plugins. (Eventually, I'll throw these into config_rename.)

If this is a problem, you might want to consider using @Filter.

One exception is x_irc, which is detected and passed to MetaResourcesFromGit properly.


In building my ultimate dist.ini file, I did a bunch of research on which modules to cram in here. As a result, this is a pretty large set of plugins, but that's exactly how I like my DZIL. Feel free to research the modules listed here, as there's a bunch of good modules that you might want to include in your own dist.ini and/or Author bundle.

Also, here's my profile.ini, if you're interested:

    template =
    append_file = plugins.ini
    root = skel
    [GenerateFile / Generate-.gitignore]
    filename = .gitignore
    is_template = 1
    content = MANIFEST
    content = MANIFEST.bak
    content = Makefile
    content = Makefile.old
    content = Build
    content = Build.bat
    content = META.*
    content = MYMETA.*
    content = .build/
    content = _build/
    content = blib/
    content = inc/
    content = .lwpcookies
    content = .last_cover_stats
    content = nytprof.out
    content = pod2htm*.tmp
    content = pm_to_blib
    content = {{$dist->name}}-*
    content = {{$dist->name}}-*.tar.gz
    commit_message = Initial commit


The project homepage is

The latest version of this module is available from the Comprehensive Perl Archive Network (CPAN). Visit to find a CPAN site near you, or see


Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is, please read this excellent guide: Please be courteous and patient when talking to us, as we might be busy or sleeping! You can join those networks/channels and get help:

Bugs / Feature Requests

Please report any bugs or feature requests via


Brendan Byrd <>


Brendan Byrd <>


This software is Copyright (c) 2013 by Brendan Byrd.

This is free software, licensed under:

  The Artistic License 2.0 (GPL Compatible)