App-CPANtoRPM

 view release on metacpan or  search on metacpan

bin/cpantorpm.pod  view on Meta::CPAN

the feature perl=5.24.1 but the module requires perl=5.008001,
rpmbuild may fail because it doesn't know how to compare these two
version numbers to know whether the requirement is met.  When this
happens, rpmbuild will fail due to missing dependencies.

In this cae, you could reformat the dependency version by passing in:

   --repl-require perl=5.08.1

=item B<-m, --macros>

Use the macro form of common SPEC constructs over the environment variable
form (e.g. %{buildroot} vs $RPM_BUILD_ROOT).

=item B<--build-rec, --test-rec, --runtime-rec>

Many modules have a list of modules that are recommended to be
installed at build time, test time, or at run time, but they are not
absolutely required.  By default, these modules will not be included
as requirements for the various steps.  Adding these options will
require them.

=back

=head2 Module Build Options

The perl module must be built as part of the process.  The following
options are used during the build:

=over 4

=item B<--build-type TYPE>

TYPE must be 'make' or 'build' and specifies that the build must be done
using the Makefile.PL or Build.PL files respectively (for those modules
that have both).  If that file does not exist, an error is triggered.

=item B<--config STRING>

The given string is passed to either the 'perl Build.PL' or 'perl
Makefile.PL' command used to configure the module and create a Build
script or a Makefile.  This option can be passed in any number of
times, but only a single option should be included in each STRING.
B<STRING> is passed in as a command line argument:

   perl Makefile.PL STRING
   perl Build.PL STRING

Since the arguments passed in differ when using a Makefile.PL and a
Build.PL procedure, for safety, you should always include the B<--build-type>
option when using this option.

=item B<--build STRING>

Similar to the B<--config> option except this passes strings which
are passed to either the './Build' or 'make' command used to actually
build the module.  This option can be passed in any number of times.

=item B<--config-input STRING>

Sometimes, the configure step prompts for input that cannot be set
using an environment variable.  In this case, this option may be used
to pass in a single line of input to the 'perl Build.PL' or 'perl
Makefile.PL' command used to configure the module and create a Build
script or a Makefile.  This option can be passed in any number of
times, but each value should include a single line of input.  This will
result in the following:

   echo STRING | perl Makefile.PL
   echo STRING | perl Build.PL

Since the arguments passed in differ when using a Makefile.PL and a
Build.PL procedure, for safety, you should always include the B<--build-type>
option when using this option.

=item B<--build-input STRING>

Similar to the B<--config-input> option except this passes strings which
are passed to either the './Build' or 'make' command used to actually
build the module.  This option can be passed in any number of times.

=item B<-T/--install-type TYPE>

=item B<-i/--install-base DIR>

These options allow you to specify where the module will be installed.
By default, the module will be built to install in the standard
perl location.  In most cases, that would mean installing the module,
documentation, and scripts in:

   BASEDIR/lib/perl5/PERLVERS
   BASEDIR/man
   BASEDIR/bin

where BASEDIR is the place where perl is installed (which is typically
/usr) and PERLVERS is the version directory (i.e. 5.14.2).  To install
in /usr/local instead of /usr, just use the option:

   --install-base /usr/local

To change the module installation directory (but not the directory of the
documentation or scripts) to either the site_perl or vendor_perl location,
use:

   --install-type site
   --install-type vendor

to set the module directory to be:

   BASEDIR/lib/perl5/site_perl/PERLVERS
   BASEDIR/lib/perl5/vendor_perl/PERLVERS

respectively.

The B<--install-type> value must be one of:

   perl  (or core)
   site
   vendor

and defaults to 'perl'.  'perl' and 'core' are synonyms.  If this is



( run in 1.218 second using v1.01-cache-2.11-cpan-6aa56a78535 )