dist::zilla::plugin::prereqs(3pm) [debian man page]

Dist::Zilla::Plugin::Prereqs(3pm)			User Contributed Perl Documentation			 Dist::Zilla::Plugin::Prereqs(3pm)

NAME

       Dist::Zilla::Plugin::Prereqs - list simple prerequisites

VERSION

       version 4.300020

SYNOPSIS

       In your dist.ini:

	 [Prereqs]
	 Foo::Bar = 1.002
	 MRO::Compat = 10
	 Sub::Exporter = 0

       You can specify requirements for different phases and relationships with:

	 [Prereqs]
	 -phase = test
	 -relationship = recommends

	 Fitz::Fotz    = 1.23
	 Text::SoundEx = 3

       Remember that if you load two Prereqs plugins, each will needs its own name, added like this:

	 [Prereqs / PluginName]
	 -phase = test
	 -relationship = recommends

	 Fitz::Fotz    = 1.23
	 Text::SoundEx = 3

       If the name is the CamelCase concatenation of a phase and relationship (or just a relationship), it will set those parameters implicitly.
       If you use a custom name, but it does not specify the relationship, and you didn't specify either "-phase" or "-relationship", it throws
       the error "No -phase or -relationship specified".  This is to prevent a typo that makes the name meaningless from slipping by unnoticed.

       The example below is equivalent to the example above, except for the name of the resulting plugin:

	 [Prereqs / TestRecommends]
	 Fitz::Fotz    = 1.23
	 Text::SoundEx = 3

DESCRIPTION

       This module adds "fixed" prerequisites to your distribution.  These are prereqs with a known, fixed minimum version that doens't change
       based on platform or other conditions.

       You can specify prerequisites for different phases and kinds of relationships.  In "RuntimeRequires", the phase is Runtime and the
       relationship is Requires.  These are described in more detail in the CPAN::Meta specification.

       The phases are:

       o   configure

       o   build

       o   test

       o   runtime

       o   develop

       The relationship types are:

       o   requires

       o   recommends

       o   suggests

       o   conflicts

       If the phase is omitted, it will default to runtime; thus, specifying "Prereqs / Recommends" in your dist.ini is equivalent to
       RuntimeRecommends.

       Not all of these phases are useful for all tools, especially tools that only understand version 1.x CPAN::Meta files.

SEE ALSO

       o   Core Dist::Zilla plugins: @Basic, AutoPrereqs.

       o   The CPAN Meta specification: "PREREQUISITES" in CPAN::Meta.

AUTHOR

       Ricardo SIGNES <rjbs@cpan.org>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2012 by Ricardo SIGNES.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-06-21					 Dist::Zilla::Plugin::Prereqs(3pm)

CPAN::Meta::Prereqs(3)					User Contributed Perl Documentation				    CPAN::Meta::Prereqs(3)

NAME

       CPAN::Meta::Prereqs - a set of distribution prerequisites by phase and type

VERSION

       version 2.120921

DESCRIPTION

       A CPAN::Meta::Prereqs object represents the prerequisites for a CPAN distribution or one of its optional features.  Each set of prereqs is
       organized by phase and type, as described in CPAN::Meta::Prereqs.

METHODS

   new
	 my $prereq = CPAN::Meta::Prereqs->new( \%prereq_spec );

       This method returns a new set of Prereqs.  The input should look like the contents of the "prereqs" field described in CPAN::Meta::Spec,
       meaning something more or less like this:

	 my $prereq = CPAN::Meta::Prereqs->new({
	   runtime => {
	     requires => {
	       'Some::Module' => '1.234',
	       ...,
	     },
	     ...,
	   },
	   ...,
	 });

       You can also construct an empty set of prereqs with:

	 my $prereqs = CPAN::Meta::Prereqs->new;

       This empty set of prereqs is useful for accumulating new prereqs before finally dumping the whole set into a structure or string.

   requirements_for
	 my $requirements = $prereqs->requirements_for( $phase, $type );

       This method returns a CPAN::Meta::Requirements object for the given phase/type combination.  If no prerequisites are registered for that
       combination, a new CPAN::Meta::Requirements object will be returned, and it may be added to as needed.

       If $phase or $type are undefined or otherwise invalid, an exception will be raised.

   with_merged_prereqs
	 my $new_prereqs = $prereqs->with_merged_prereqs( $other_prereqs );

	 my $new_prereqs = $prereqs->with_merged_prereqs( @other_prereqs );

       This method returns a new CPAN::Meta::Prereqs objects in which all the other prerequisites given are merged into the current set.  This is
       primarily provided for combining a distribution's core prereqs with the prereqs of one of its optional features.

       The new prereqs object has no ties to the originals, and altering it further will not alter them.

   as_string_hash
       This method returns a hashref containing structures suitable for dumping into a distmeta data structure.  It is made up of hashes and
       strings, only; there will be no Prereqs, CPAN::Meta::Requirements, or "version" objects inside it.

   is_finalized
       This method returns true if the set of prereqs has been marked "finalized," and cannot be altered.

   finalize
       Calling "finalize" on a Prereqs object will close it for further modification.  Attempting to make any changes that would actually alter
       the prereqs will result in an exception being thrown.

   clone
	 my $cloned_prereqs = $prereqs->clone;

       This method returns a Prereqs object that is identical to the original object, but can be altered without affecting the original object.
       Finalization does not survive cloning, meaning that you may clone a finalized set of prereqs and then modify the clone.

BUGS

       Please report any bugs or feature using the CPAN Request Tracker.  Bugs can be submitted through the web interface at
       <http://rt.cpan.org/Dist/Display.html?Queue=CPAN-Meta>

       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.

AUTHORS

       o   David Golden <dagolden@cpan.org>

       o   Ricardo Signes <rjbs@cpan.org>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2010 by David Golden and Ricardo Signes.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.16.3							    2012-04-01						    CPAN::Meta::Prereqs(3)