1N/A# List explicitly here the variables you want Configure to 1N/A# generate. Metaconfig only looks for shell variables, so you 1N/A# have to mention them as if they were shell variables, not 1N/A# %Config entries. Thus you write 1N/A# to ensure Configure will look for $Config{startperl}. 1N/A# This forces PL files to create target in same directory as PL file. 1N/A# This is so that make depend always knows where to find PL derivatives. 1N/Aopen OUT,
">$file" or die "Can't create $file: $!";
1N/Aprint "Extracting $file (with variable substitutions)\n";
1N/A# In this section, perl variables will be expanded during extraction. 1N/A# You can use $Config{...} to use Configure variables. 1N/A eval 'exec perl -S \$0 "\$@"' 1N/A# In the following, perl variables are not expanded during extraction. 1N/A############################################################################# 1N/A# pod2usage -- command to print usage messages from embedded pod docs 1N/A# Copyright (c) 1996-2000 by Bradford Appleton. All rights reserved. 1N/A# This file is part of "PodParser". PodParser is free software; 1N/A# you can redistribute it and/or modify it under the same terms 1N/A############################################################################# 1N/Apod2usage - print usage messages from embedded pod docs in files 1N/A[B<-exit>S< >I<exitval>] 1N/A[B<-output>S< >I<outfile>] 1N/A[B<-verbose> I<level>] 1N/A[B<-pathlist> I<dirlist>] 1N/A=head1 OPTIONS AND ARGUMENTS 1N/APrint a brief help message and exit. 1N/APrint this command's manual page and exit. 1N/A=item B<-exit> I<exitval> 1N/AThe exit status value to return. 1N/A=item B<-output> I<outfile> 1N/AThe output file to print to. If the special names "-" or ">&1" or ">&STDOUT" 1N/Aare used then standard output is used. If ">&2" or ">&STDERR" is used then 1N/Astandard error is used. 1N/A=item B<-verbose> I<level> 1N/AThe desired level of verbosity to use: 1N/A 1 : print SYNOPSIS only 1N/A 3 : print the entire manpage (similar to running pod2text) 1N/A=item B<-pathlist> I<dirlist> 1N/ASpecifies one or more directories to search for the input file if it 1N/Awas not supplied with an absolute path. Each directory path in the given 1N/Alist should be separated by a ':' on Unix (';' on MSWin32 and DOS). 1N/AThe pathname of a file containing pod documentation to be output in 1N/Ausage mesage format (defaults to standard input). 1N/AB<pod2usage> will read the given input file looking for pod 1N/Adocumentation and will print the corresponding usage message. 1N/AIf no input file is specifed than standard input is read. 1N/AB<pod2usage> invokes the B<pod2usage()> function in the B<Pod::Usage> 1N/AL<Pod::Usage>, L<pod2text(1)> 1N/ABrad Appleton E<lt>bradapp@enteract.comE<gt> 1N/ABased on code for B<pod2text(1)> written by 1N/ATom Christiansen E<lt>tchrist@mox.perl.comE<gt> 1N/A## Dont default to STDIN if connected to a terminal 1N/A print STDERR "pod2usage: Too many filenames given\n\n";
1N/Aclose OUT or die "Can't close $file: $!";
1N/Achmod 0755, $
file or die "Can't reset permissions for $file: $!\n";
1N/Aexec(
"$Config{'eunicefix'} $file")
if $
Config{
'eunicefix'}
ne ':';