view release on metacpan or  search on metacpan

dist.ini  view on Meta::CPAN

applyto_map = develop.suggests = develop.suggests
applyto_phase = develop
modules = Dist::Zilla::PluginBundle::Author::KENTNL
modules = Dist::Zilla::App::Command::bakeini

[RemovePrereqs::Provided / @Author::KENTNL/RemovePrereqs::Provided]

[Prereqs / @Author::KENTNL/::Role::BundleDeps]
; auto_prereqs_skip = File::Find
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
Dist::Zilla::Plugin::BumpVersionAfterRelease = 0
Dist::Zilla::Plugin::ConfirmRelease = 0
Dist::Zilla::Plugin::CopyFilesFromBuild = 0
Dist::Zilla::Plugin::Git::Check = 0
Dist::Zilla::Plugin::Git::Commit = 0
Dist::Zilla::Plugin::Git::CommitBuild = 0

lib/Dist/Zilla/Plugin/Prereqs/Recommend/MatchInstalled.pm  view on Meta::CPAN

it propagates the upgrade to a different relation, to produce a softer dependency map.

Below shows the defaults expanded by hand.

    [Prereqs::Recommend::MatchInstalled]
    applyto_phase = configure
    applyto_phase = runtime
    applyto_phase = test
    applyto_phase = build
    applyto_phase = develop
    source_relation = requires
    target_relation = recommends

And add these stanzas for example:

    modules = Module::Build
    modules = Moose

And you have yourself a distribution that won't needlessly increase the dependencies
on either, but will add increased dependencies to the C<recommends> phase.

lib/Dist/Zilla/Plugin/Prereqs/Recommend/MatchInstalled.pm  view on Meta::CPAN

Valuable values are:

    build test runtime configure develop

And those are the default values too.

=head2 C<source_relation>

    [Prereqs::Recommend::MatchInstalled]
    source_relation = requires

This attribute specifies the prerequisites to skim for modules to recommend upgrades on.

Valuable values are:

    requires recommends suggests

Lastly:

    conflicts