- BUNDLED PLUGIN OPTIONS
- SEE ALSO
- COPYRIGHT AND LICENSE
Dist::Zilla::PluginBundle::RSRCHBOY - Zilla your distributions like RSRCHBOY!
This document describes version 0.075 of Dist::Zilla::PluginBundle::RSRCHBOY - released May 08, 2017 as part of Dist-Zilla-PluginBundle-RSRCHBOY.
# in your dist.ini... [@RSRCHBOY]
This is RSRCHBOY's current Dist::Zilla
dist.ini config for his packages. He's still figuring this all out. It's like vim, you never really know all the things.
If you'd like to see what this does without digging into the guts, I recommend you install the most excellent Dist::Zilla::App::Command::dumpphases package. This will give you a new dzil command, allowing you to see a sensible dump of what plugins are going to be used, etc.
Plugin configuration for public release.
Plugins that mess about with what goes into META.*.
Preps plugin lists / config; see Dist::Zilla::Role::PluginBundle::Easy.
A list of words our POD spell checker should ignore.
On release, use your gpg key to sign the version tag created (if you're using git) and also generate a SIGNATURE file.
See also Dist::Zilla::Plugin::Signature.
If set to a true value, we'll use Dist::Zilla::Plugin::Twitter to tweet when a release occurs.
This enables various GitHub related plugins to update distribution and GitHub metadata automatically.
After a release, install the distribution locally. Our default install command is (from inside the built release directory):
You can change this by setting the
It's possible to pass options to our bundled plugins directly:
; format is Plugin::Name.option [@RSRCHBOY] GatherDir.exclude_filename = cpanfile
For information on specific plugins and their options, you should refer to the documentation of Dist::Zilla::Role::PluginBundle::Config::Slicer.
Please see those modules/websites for more information related to this module.
Please report any bugs or feature requests on the bugtracker website https://github.com/RsrchBoy/dist-zilla-pluginbundle-rsrchboy/issues
When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.
Chris Weyl <firstname.lastname@example.org>
Neil Bowers <email@example.com>
Sergey Romanov <firstname.lastname@example.org>
This software is Copyright (c) 2017, 2016, 2015, 2014, 2013, 2012, 2011 by Chris Weyl.
This is free software, licensed under:
The GNU Lesser General Public License, Version 2.1, February 1999