Perl-Configure
view release on metacpan or search on metacpan
lib/Perl/Configure.pm view on Meta::CPAN
| path-html-site | Pathname where the |
| | site-specific html pages |
| | should be installed |
| path-install | What installation prefix |
| | should I use for installing |
| | files? |
| path-man-lib-site | Pathname where the |
| | site-specific library manual |
| | pages should be installed? |
| path-man-lib-src | Where do the perl5 library |
| | man pages (source) go? |
| path-man-site | Pathname where the |
| | site-specific manual pages |
| | should be installed |
| path-man-src | Where do the main Perl5 |
| | manual pages (source) go? |
| path-module-html | Directory for the Perl5 |
| | module html pages? |
| path-perl-html | Directory for the main Perl5 |
| | html pages? |
| path-private | Pathname where the private |
| | library files will reside? |
| path-public-arch | Other username to test |
| | security of setuid scripts |
| | with? |
| path-public-exe | Where do you keep publicly |
| | executable scripts? |
| path-shebang | What shall I put after the #! |
| | to start up perl |
| path-site-specific | Pathname for the |
| | site-specific library files? |
| path-site-specific-arch | Pathname for the |
| | site-specific |
| | architecture-dependent |
| | library files? |
| path-vendor-specific | Pathname for the |
| | vendor-supplied library |
| | files? |
| path-vendor-specific-arch | Pathname for vendor-supplied |
| | architecture-dependent files? |
| path-vendor-specific-bin | Pathname for the |
| | vendor-supplied executables |
| | directory? |
| path-vendor-specific-html | Pathname for the |
| | vendor-supplied html pages? |
| path-vendor-specific-man1 | Pathname for the |
| | vendor-supplied manual |
| | section 1 pages? |
| path-vendor-specific-man3 | Pathname for the |
| | vendor-supplied manual |
| | section 3 pages? |
| path-vendor-specific-scri | Pathname for the |
| pts | vendor-supplied scripts |
| | directory? |
| perlio | Use the PerlIO abstraction |
| | layer? |
| prefix | Installation prefix to use? |
| previous-keep | Keep the previous value |
| random-func | Use which function to |
| | generate random numbers? |
| relocatable-inc | Use relocatable @INC? |
| setuid-emu | Do you want to do |
| | setuid/setgid emulation? |
| setuid-secure | Does your kernel have |
| | *secure* setuid scripts? |
| shell-escape | Press return or use a shell |
| | escape to edit config.sh |
| socks | Build Perl for SOCKS? |
| static-extensions | What extensions do you wish |
| | to load statically? |
| threads | Build a threading Perl? |
| usrbinperl | Do you want to install perl |
| | as /usr/bin/perl |
| vendor-specific | Do you want to configure |
| | vendor-specific add-on |
| | directories? |
| vendor-specific-prefix | Installation prefix to use |
| | for vendor-supplied add-ons |
| version-specific-only | Do you want to install only |
| | the version-specific parts of |
| | perl? |
| vfork | Do you still want to use |
| | vfork() |
'---------------------------+-------------------------------'
=for TABLE_END
Perl::Configure requires an existing perl installation with a number
of CPAN modules (Expect amongst them), so it can't be used to
bootstrap a machine without a fully functional perl interpreter.
=head1 EXAMPLES
If you want to make sure that a previously generated C<config.sh> file's
content is used as a default and that any discrepancies are kept, use
C<config-sh> and C<previous-keep>.
my $cfg = Perl::Configure->new();
$cfg->define( "config-sh" => 'y',
"previous-keep" => 'y',
);
$cfg->run();
If you specify a prefix path that doesn't exist (yet), make sure to
set C<dir-check> to 'y' to answer Configure's question appropriately:
$cfg->define( "prefix" => '/quack',
"dir-check" => 'y',
);
=head1 ADDING QUESTIONS
The questions that C<Perl::Configure> recognizes are stored in
the __DATA__ section of C<Perl::Configure::Questions> in YAML
format. New releases of C<Perl::Configure> might add to this section
(or change its format, so don't rely on it, use the API instead).
If you encounter a C<Configure> question that C<Perl::Configure> doesn't
recognize (and therefore first hangs and then aborts), the best way to
fix this is submit the question, a proposed token name and a sample
( run in 1.711 second using v1.01-cache-2.11-cpan-71847e10f99 )