Edit: /usr/bin/perlthanks (44726B)
#!/usr/bin/perl
eval 'exec /usr/bin/perl -S $0 ${1+"$@"}'
if $running_under_some_shell;
my $config_tag1 = '5.10.1';
my $patch_tags = '';
my @patches = (
''
);
use warnings;
no warnings 'once'; # Eventually, the $::opt_ stuff should get cleaned up
use strict;
use Config;
use File::Spec; # keep perlbug Perl 5.005 compatible
use Getopt::Std;
use File::Basename 'basename';
sub paraprint;
BEGIN {
eval { require Mail::Send;};
$::HaveSend = ($@ eq "");
eval { require Mail::Util; } ;
$::HaveUtil = ($@ eq "");
# use secure tempfiles wherever possible
eval { require File::Temp; };
$::HaveTemp = ($@ eq "");
eval { require Module::CoreList; };
$::HaveCoreList = ($@ eq "");
};
my $Version = "1.39";
# Changed in 1.06 to skip Mail::Send and Mail::Util if not available.
# Changed in 1.07 to see more sendmail execs, and added pipe output.
# Changed in 1.08 to use correct address for sendmail.
# Changed in 1.09 to close the REP file before calling it up in the editor.
# Also removed some old comments duplicated elsewhere.
# Changed in 1.10 to run under VMS without Mail::Send; also fixed
# temp filename generation.
# Changed in 1.11 to clean up some text and removed Mail::Send deactivator.
# Changed in 1.12 to check for editor errors, make save/send distinction
# clearer and add $ENV{REPLYTO}.
# Changed in 1.13 to hopefully make it more difficult to accidentally
# send mail
# Changed in 1.14 to make the prompts a little more clear on providing
# helpful information. Also let file read fail gracefully.
# Changed in 1.15 to add warnings to stop people using perlbug for non-bugs.
# Also report selected environment variables.
# Changed in 1.16 to include @INC, and allow user to re-edit if no changes.
# Changed in 1.17 Win32 support added. GSAR 97-04-12
# Changed in 1.18 add '-ok' option for reporting build success. CFR 97-06-18
# Changed in 1.19 '-ok' default not '-v'
# add local patch information
# warn on '-ok' if this is an old system; add '-okay'
# Changed in 1.20 Added patchlevel.h reading and version/config checks
# Changed in 1.21 Added '-nok' for reporting build failure DFD 98-05-05
# Changed in 1.22 Heavy reformatting & minor bugfixes HVDS 98-05-10
# Changed in 1.23 Restore -ok(ay): say 'success'; don't prompt
# Changed in 1.24 Added '-F
' to save report HVDS 98-07-01
# Changed in 1.25 Warn on failure to open save file. HVDS 98-07-12
# Changed in 1.26 Don't require -t STDIN for -ok. HVDS 98-07-15
# Changed in 1.27 Added Mac OS and File::Spec support CNANDOR 99-07-27
# Changed in 1.28 Additional questions for Perlbugtron RFOLEY 20.03.2000
# Changed in 1.29 Perlbug(tron): auto(-ok), short prompts RFOLEY 05-05-2000
# Changed in 1.30 Added warnings on failure to open files MSTEVENS 13-07-2000
# Changed in 1.31 Add checks on close().Fix my $var unless. TJENNESS 26-07-2000
# Changed in 1.32 Use File::Spec->tmpdir TJENNESS 20-08-2000
# Changed in 1.33 Don't require -t STDOUT for -ok.
# Changed in 1.34 Added Message-Id RFOLEY 18-06-2002
# Changed in 1.35 Use File::Temp (patch from Solar Designer) NWCLARK 28-02-2004
# Changed in 1.36 Initial Module::CoreList support Alexandr Ciornii 11-07-2007
# Changed in 1.37 Killed some string evals, rewrote most prose JESSE 2008-06-08
# Changed in 1.38 Actually enforce the CoreList check,
# Record the module the user enters if they do so
# Refactor prompts to use common code JESSE 2008-06-08
# Changed in 1.39 Trap mail sending failures (simple ones) so JESSE 2008-06-08
# users might be able to recover their bug reports
# Refactor mail sending routines
# Unify message building code
# Unify message header building
# Fix "module" prompting to not squish "category" prompting
# use warnings; (except 'once' warnings)
# Unified report fingerprint/change detection code
# Removed some labeled 'gotos'
#TODO:
# make sure failure (transmission-wise) of Mail::Send is accounted for.
# (This may work now. Unsure of the original author's issue -JESSE 2008-06-08)
# - Test -b option
my( $file, $usefile, $cc, $address, $bugaddress, $testaddress, $thanksaddress,
$filename, $messageid, $domain, $subject, $from, $verbose, $ed, $outfile,
$fh, $me, $body, $andcc, %REP, $ok, $thanks, $progname,
$Is_MacOS, $Is_MSWin32, $Is_Linux, $Is_VMS, $Is_OpenBSD,
$report_about_module, $category, $severity,
);
my $perl_version = $^V ? sprintf("%vd", $^V) : $];
my $config_tag2 = "$perl_version - $Config{cf_time}";
Init();
if ($::opt_h) { Help(); exit; }
if ($::opt_d) { Dump(*STDOUT); exit; }
if (!-t STDIN && !($ok and not $::opt_n)) {
paraprint <<"EOF";
Please use $progname interactively. If you want to
include a file, you can use the -f switch.
EOF
die "\n";
}
Query();
Edit() unless $usefile || ($ok and not $::opt_n);
NowWhat();
if ($outfile) {
save_message_to_disk($outfile);
} else {
Send();
if ($thanks) {
print "\nThank you for taking the time to send a thank-you message!\n\n";
} else {
print "\nThank you for taking the time to file a bug report!\n\n";
}
}
exit;
sub ask_for_alternatives { # (category|severity)
my $name = shift;
my %alts = (
'category' => {
'default' => 'core',
'ok' => 'install',
# Inevitably some of these will end up in RT whatever we do:
'thanks' => 'thanks',
'opts' => [qw(core docs install library utilities)], # patch, notabug
},
'severity' => {
'default' => 'low',
'ok' => 'none',
'thanks' => 'none',
'opts' => [qw(critical high medium low wishlist none)], # zero
},
);
die "Invalid alternative ($name) requested\n" unless grep(/^$name$/, keys %alts);
my $alt = "";
my $what = $ok || $thanks;
if ($what) {
$alt = $alts{$name}{$what};
} else {
my @alts = @{$alts{$name}{'opts'}};
print "\n\n";
paraprint < 5) {
die "Invalid $name: aborting.\n";
}
$alt = _prompt('', "\u$name", $alts{$name}{'default'});
$alt ||= $alts{$name}{'default'};
} while !((($alt) = grep(/^$alt/i, @alts)));
}
lc $alt;
}
sub Init {
# -------- Setup --------
$Is_MSWin32 = $^O eq 'MSWin32';
$Is_VMS = $^O eq 'VMS';
$Is_Linux = lc($^O) eq 'linux';
$Is_OpenBSD = lc($^O) eq 'openbsd';
$Is_MacOS = $^O eq 'MacOS';
@ARGV = split m/\s+/,
MacPerl::Ask('Provide command line args here (-h for help):')
if $Is_MacOS && $MacPerl::Version =~ /App/;
if (!getopts("Adhva:s:b:f:F:r:e:SCc:to:n:T")) { Help(); exit; };
# This comment is needed to notify metaconfig that we are
# using the $perladmin, $cf_by, and $cf_time definitions.
# -------- Configuration ---------
# perlbug address
$bugaddress = 'perlbug@perl.org';
# Test address
$testaddress = 'perlbug-test@perl.org';
# Thanks address
$thanksaddress = 'perl-thanks@perl.org';
if (basename ($0) =~ /^perlthanks/i) {
# invoked as perlthanks
$::opt_T = 1;
$::opt_C = 1; # don't send a copy to the local admin
}
if ($::opt_T) {
$thanks = 'thanks';
}
$progname = $thanks ? 'perlthanks' : 'perlbug';
# Target address
$address = $::opt_a || ($::opt_t ? $testaddress
: $thanks ? $thanksaddress : $bugaddress);
# Users address, used in message and in Reply-To header
$from = $::opt_r || "";
# Include verbose configuration information
$verbose = $::opt_v || 0;
# Subject of bug-report message
$subject = $::opt_s || "";
# Send a file
$usefile = ($::opt_f || 0);
# File to send as report
$file = $::opt_f || "";
# File to output to
$outfile = $::opt_F || "";
# Body of report
$body = $::opt_b || "";
# Editor
$ed = $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT}
|| ($Is_VMS && "edit/tpu")
|| ($Is_MSWin32 && "notepad")
|| ($Is_MacOS && '')
|| "vi";
# Not OK - provide build failure template by finessing OK report
if ($::opt_n) {
if (substr($::opt_n, 0, 2) eq 'ok' ) {
$::opt_o = substr($::opt_n, 1);
} else {
Help();
exit();
}
}
# OK - send "OK" report for build on this system
$ok = '';
if ($::opt_o) {
if ($::opt_o eq 'k' or $::opt_o eq 'kay') {
# force these options
unless ($::opt_n) {
$::opt_S = 1; # don't prompt for send
$::opt_b = 1; # we have a body
$body = "Perl reported to build OK on this system.\n";
}
$::opt_C = 1; # don't send a copy to the local admin
$::opt_s = 1; # we have a subject line
$subject = ($::opt_n ? 'Not ' : '')
. "OK: perl $perl_version ${patch_tags}on"
." $::Config{'archname'} $::Config{'osvers'} $subject";
$ok = 'ok';
} else {
Help();
exit();
}
}
# Possible administrator addresses, in order of confidence
# (Note that cf_email is not mentioned to metaconfig, since
# we don't really want it. We'll just take it if we have to.)
#
# This has to be after the $ok stuff above because of the way
# that $::opt_C is forced.
$cc = $::opt_C ? "" : (
$::opt_c || $::Config{'perladmin'}
|| $::Config{'cf_email'} || $::Config{'cf_by'}
);
if ($::HaveUtil) {
$domain = Mail::Util::maildomain();
} elsif ($Is_MSWin32) {
$domain = $ENV{'USERDOMAIN'};
} else {
require Sys::Hostname;
$domain = Sys::Hostname::hostname();
}
# Message-Id - rjsf
$messageid = "<$::Config{'version'}_${$}_".time."\@$domain>";
# My username
$me = $Is_MSWin32 ? $ENV{'USERNAME'}
: $^O eq 'os2' ? $ENV{'USER'} || $ENV{'LOGNAME'}
: $Is_MacOS ? $ENV{'USER'}
: eval { getpwuid($<) }; # May be missing
$from = $::Config{'cf_email'}
if !$from && $::Config{'cf_email'} && $::Config{'cf_by'} && $me &&
($me eq $::Config{'cf_by'});
} # sub Init
sub Query {
# Explain what perlbug is
unless ($ok) {
if ($thanks) {
paraprint <<'EOF';
This program provides an easy way to send a thank-you message back to the
authors and maintainers of perl.
If you wish to submit a bug report, please run it without the -T flag
(or run the program perlbug rather than perlthanks)
EOF
} else {
paraprint <<"EOF";
This program provides an easy way to create a message reporting a
bug in the core perl distribution (along with tests or patches)
to the volunteers who maintain perl at $address. To send a thank-you
note to $thanksaddress instead of a bug report, please run 'perlthanks'.
Please do not use $0 to send test messages, test whether perl
works, or to report bugs in perl modules from CPAN.
For help using perl, try posting to the Usenet newsgroup
comp.lang.perl.misc.
EOF
}
}
# Prompt for subject of message, if needed
if ($subject && TrivialSubject($subject)) {
$subject = '';
}
unless ($subject) {
print
"First of all, please provide a subject for the message.\n";
if ( not $thanks) {
paraprint <first_release($entry);
if ($entry and not $first_release) {
paraprint <$filename") or die "Unable to create report file '$filename': $!\n";
my $reptype = !$ok ? ($thanks ? 'thank-you' : 'bug')
: $::opt_n ? "build failure" : "success";
print REP <) {
print REP $_
}
close(F) or die "Error closing '$file': $!";
} else {
if ($thanks) {
print REP <<'EOF';
-----------------------------------------------------------------
[Please enter your thank-you message here]
[You're welcome to delete anything below this line]
-----------------------------------------------------------------
EOF
} else {
print REP <<'EOF';
-----------------------------------------------------------------
[Please describe your issue here]
[Please do not change anything below this line]
-----------------------------------------------------------------
EOF
}
}
Dump(*REP);
close(REP) or die "Error closing report file: $!";
# Set up an initial report fingerprint so we can compare it later
_fingerprint_lines_in_report();
} # sub Query
sub Dump {
local(*OUT) = @_;
print OUT <etry dit
next;
} elsif ( $action =~ /^[cq]/i ) { # ancel, uit
Cancel(); # cancel exits
}
}
# Ok. the user did what they needed to;
return;
}
}
sub Cancel {
1 while unlink($filename); # remove all versions under VMS
print "\nQuitting without sending your message.\n";
exit(0);
}
sub NowWhat {
# Report is done, prompt for further action
if( !$::opt_S ) {
while(1) {
my $menu = <ile/ve
if ( SaveMessage() ) { exit }
} elsif ($action =~ /^(d|l|sh)/i ) { # isplay, ist, ow
# Display the message
open(REP, "<$filename") or die "Couldn't open file '$filename': $!\n";
while () { print $_ }
close(REP) or die "Error closing report file '$filename': $!";
} elsif ($action =~ /^su/i) { # bject
my $reply = _prompt( "Subject: $subject", "If the above subject is fine, press Enter. Otherwise, type a replacement now\nSubject");
if ($reply ne '') {
unless (TrivialSubject($reply)) {
$subject = $reply;
print "Subject: $subject\n";
}
}
} elsif ($action =~ /^se/i) { # end
# Send the message
my $reply = _prompt( "Are you certain you want to send this message?", 'Please type "yes" if you are','no');
if ($reply =~ /^yes$/) {
last;
} else {
paraprint <dit, e-edit
# edit the message
Edit();
} elsif ($action =~ /^[qc]/i) { # ancel, uit
Cancel();
} elsif ($action =~ /^s/i) {
paraprint < 1);
close($fh);
return $filename;
} else {
# Bah. Fall back to doing things less securely.
my $dir = File::Spec->tmpdir();
$filename = "bugrep0$$";
$filename++ while -e File::Spec->catfile($dir, $filename);
$filename = File::Spec->catfile($dir, $filename);
}
}
sub paraprint {
my @paragraphs = split /\n{2,}/, "@_";
for (@paragraphs) { # implicit local $_
s/(\S)\s*\n/$1 /g;
write;
print "\n";
}
}
sub _prompt {
my ($explanation, $prompt, $default) = (@_);
if ($explanation) {
print "\n\n";
paraprint $explanation;
}
print $prompt. ($default ? " [$default]" :''). ": ";
my $result = scalar(<>);
chomp($result);
$result =~ s/^\s*(.*?)\s*$/$1/s;
if ($default && $result eq '') {
return $default;
} else {
return $result;
}
}
sub _build_header {
my %attr = (@_);
my $head = '';
for my $header (keys %attr) {
$head .= "$header: ".$attr{$header}."\n";
}
return $head;
}
sub _message_headers {
my %headers = ( To => $address, Subject => $subject );
$headers{'Cc'} = $cc if ($cc);
$headers{'Message-Id'} = $messageid if ($messageid);
$headers{'Reply-To'} = $from if ($from);
return \%headers;
}
sub build_complete_message {
my $content = _build_header(%{_message_headers()}) . "\n\n";
open( REP, "<$filename" ) or die "Couldn't open file '$filename': $!\n";
while () { $content .= $_; }
close(REP) or die "Error closing report file '$filename': $!";
return $content;
}
sub save_message_to_disk {
my $file = shift;
open OUTFILE, ">$file" or do { warn "Couldn't open '$file': $!\n"; return undef};
print OUTFILE build_complete_message();
close(OUTFILE) or do { warn "Error closing $file: $!"; return undef };
print "\nMessage saved.\n";
return 1;
}
sub _send_message_vms {
if ( ( $address =~ /@/ and $address !~ /^\w+%"/ )
or ( $cc =~ /@/ and $cc !~ /^\w+%"/ ) ) {
my $prefix;
foreach ( qw[ IN MX SMTP UCX PONY WINS ], '' ) {
$prefix = "$_%", last if $ENV{"MAIL\$PROTOCOL_$_"};
}
$address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
$cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
}
$subject =~ s/"/""/g;
$address =~ s/"/""/g;
$cc =~ s/"/""/g;
my $sts = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
if ($sts) {
die "Can't spawn off mail (leaving bug report in $filename): $sts";
}
}
sub _send_message_mailsend {
my $msg = Mail::Send->new();
my %headers = %{_message_headers()};
for my $key ( keys %headers) {
$msg->add($key => $headers{$key});
}
$fh = $msg->open;
open(REP, "<$filename") or die "Couldn't open '$filename': $!\n";
while () { print $fh $_ }
close(REP) or die "Error closing $filename: $!";
$fh->close;
print "\nMessage sent.\n";
}
sub _probe_for_sendmail {
my $sendmail = "";
for (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail)) {
$sendmail = $_, last if -e $_;
}
if ( $^O eq 'os2' and $sendmail eq "" ) {
my $path = $ENV{PATH};
$path =~ s:\\:/:;
my @path = split /$Config{'path_sep'}/, $path;
for (@path) {
$sendmail = "$_/sendmail", last if -e "$_/sendmail";
$sendmail = "$_/sendmail.exe", last if -e "$_/sendmail.exe";
}
}
return $sendmail;
}
sub _send_message_sendmail {
my $sendmail = _probe_for_sendmail();
unless ($sendmail) {
paraprint(<<"EOF"), die "\n";
It appears that there is no program which looks like "sendmail" on
your system and that the Mail::Send library from CPAN isn't available.
Because of this, there's no easy way to automatically send your
message.
A copy of your message has been saved in '$filename' for you to
send to '$address' with your normal mail client.
EOF
}
open( SENDMAIL, "|$sendmail -t -oi" )
|| die "'|$sendmail -t -oi' failed: $!";
print SENDMAIL build_complete_message();
if ( close(SENDMAIL) ) {
print "\nMessage sent\n";
} else {
warn "\nSendmail returned status '", $? >> 8, "'\n";
}
}
# a strange way to check whether any significant editing
# has been done: check whether any new non-empty lines
# have been added.
sub _fingerprint_lines_in_report {
my $new_lines = 0;
# read in the report template once so that
# we can track whether the user does any editing.
# yes, *all* whitespace is ignored.
open(REP, "<$filename") or die "Unable to open report file '$filename': $!\n";
while (my $line = ) {
$line =~ s/\s+//g;
$new_lines++ if (!$REP{$line});
}
close(REP) or die "Error closing report file '$filename': $!";
# returns the number of lines with content that wasn't there when last we looked
return $new_lines;
}
format STDOUT =
^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
$_
.
__END__
=head1 NAME
perlbug - how to submit bug reports on Perl
=head1 SYNOPSIS
B
B S<[ B<-v> ]> S<[ B<-a> I ]> S<[ B<-s> I ]>
S<[ B<-b> I | B<-f> I ]> S<[ B<-F> I ]>
S<[ B<-r> I ]>
S<[ B<-e> I ]> S<[ B<-c> I | B<-C> ]>
S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]> S<[ B<-T> ]>
B S<[ B<-v> ]> S<[ B<-r> I ]>
S<[ B<-A> ]> S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]>
B
=head1 DESCRIPTION
This program is designed to help you generate and send bug reports
(and thank-you notes) about perl5 and the modules which ship with it.
In most cases, you can just run it interactively from a command
line without any special arguments and follow the prompts.
If you have found a bug with a non-standard port (one that was not
part of the I), a binary distribution, or a
non-core module (such as Tk, DBI, etc), then please see the
documentation that came with that distribution to determine the
correct place to report bugs.
If you are unable to send your report using B (most likely
because your system doesn't have a way to send mail that perlbug
recognizes), you may be able to use this tool to compose your report
and save it to a file which you can then send to B
using your regular mail client.
In extreme cases, B may not work well enough on your system
to guide you through composing a bug report. In those cases, you
may be able to use B to get system configuration
information to include in a manually composed bug report to
B.
When reporting a bug, please run through this checklist:
=over 4
=item What version of Perl you are running?
Type C at the command line to find out.
=item Are you running the latest released version of perl?
Look at http://www.perl.org/ to find out. If you are not using the
latest released version, please try to replicate your bug on the
latest stable release.
Note that reports about bugs in old versions of Perl, especially
those which indicate you haven't also tested the current stable
release of Perl, are likely to receive less attention from the
volunteers who build and maintain Perl than reports about bugs in
the current release.
This tool isn't apropriate for reporting bugs in any version
prior to Perl 5.0.
=item Are you sure what you have is a bug?
A significant number of the bug reports we get turn out to be
documented features in Perl. Make sure the issue you've run into
isn't intentional by glancing through the documentation that comes
with the Perl distribution.
Given the sheer volume of Perl documentation, this isn't a trivial
undertaking, but if you can point to documentation that suggests
the behaviour you're seeing is I, your issue is likely to
receive more attention. You may want to start with B
L for pointers to common traps that new (and experienced)
Perl programmers run into.
If you're unsure of the meaning of an error message you've run
across, B L for an explanation. If the message
isn't in perldiag, it probably isn't generated by Perl. You may
have luck consulting your operating system documentation instead.
If you are on a non-UNIX platform B L, as some
features may be unimplemented or work differently.
You may be able to figure out what's going wrong using the Perl
debugger. For information about how to use the debugger B
L.
=item Do you have a proper test case?
The easier it is to reproduce your bug, the more likely it will be
fixed -- if nobody can duplicate your problem, it probably won't be
addressed.
A good test case has most of these attributes: short, simple code;
few dependencies on external commands, modules, or libraries; no
platform-dependent code (unless it's a platform-specific bug);
clear, simple documentation.
A good test case is almost always a good candidate to be included in
Perl's test suite. If you have the time, consider writing your test case so
that it can be easily included into the standard test suite.
=item Have you included all relevant information?
Be sure to include the B error messages, if any.
"Perl gave an error" is not an exact error message.
If you get a core dump (or equivalent), you may use a debugger
(B, B, etc) to produce a stack trace to include in the bug
report.
NOTE: unless your Perl has been compiled with debug info
(often B<-g>), the stack trace is likely to be somewhat hard to use
because it will most probably contain only the function names and not
their arguments. If possible, recompile your Perl with debug info and
reproduce the crash and the stack trace.
=item Can you describe the bug in plain English?
The easier it is to understand a reproducible bug, the more likely
it will be fixed. Any insight you can provide into the problem
will help a great deal. In other words, try to analyze the problem
(to the extent you can) and report your discoveries.
=item Can you fix the bug yourself?
A bug report which I will almost
definitely be fixed. When sending a patch, please use the C
program with the C<-u> option to generate "unified" diff files.
Bug reports with patches are likely to receive significantly more
attention and interest than those without patches.
Your patch may be returned with requests for changes, or requests for more
detailed explanations about your fix.
Here are a few hints for creating high-quality patches:
Make sure the patch is not reversed (the first argument to diff is
typically the original file, the second argument your changed file).
Make sure you test your patch by applying it with the C
program before you send it on its way. Try to follow the same style
as the code you are trying to patch. Make sure your patch really
does work (C, if the thing you're patching is covered
by Perl's test suite).
=item Can you use C to submit the report?
B will, amongst other things, ensure your report includes
crucial information about your version of perl. If C is
unable to mail your report after you have typed it in, you may have
to compose the message yourself, add the output produced by C and email it to B. If, for some reason, you
cannot run C at all on your system, be sure to include the
entire output produced by running C (note the uppercase V).
Whether you use C or send the email manually, please make
your Subject line informative. "a bug" is not informative. Neither
is "perl crashes" nor is "HELP!!!". These don't help. A compact
description of what's wrong is fine.
=item Can you use C to submit a thank-you note?
Yes, you can do this by either using the C<-T> option, or by invoking
the program as C. Thank-you notes are good. It makes people
smile.
=back
Having done your bit, please be prepared to wait, to be told the
bug is in your code, or possibly to get no reply at all. The
volunteers who maintain Perl are busy folks, so if your problem is
an obvious bug in your own code, is difficult to understand or is
a duplicate of an existing report, you may not receive a personal
reply.
If it is important to you that your bug be fixed, do monitor the
perl5-porters@perl.org mailing list and the commit logs to development
versions of Perl, and encourage the maintainers with kind words or
offers of frosty beverages. (Please do be kind to the maintainers.
Harassing or flaming them is likely to have the opposite effect of
the one you want.)
Feel free to update the ticket about your bug on http://rt.perl.org
if a new version of Perl is released and your bug is still present.
=head1 OPTIONS
=over 8
=item B<-a>
Address to send the report to. Defaults to B.
=item B<-A>
Don't send a bug received acknowledgement to the reply address.
Generally it is only a sensible to use this option if you are a
perl maintainer actively watching perl porters for your message to
arrive.
=item B<-b>
Body of the report. If not included on the command line, or
in a file with B<-f>, you will get a chance to edit the message.
=item B<-C>
Don't send copy to administrator.
=item B<-c>
Address to send copy of report to. Defaults to the address of the
local perl administrator (recorded when perl was built).
=item B<-d>
Data mode (the default if you redirect or pipe output). This prints out
your configuration data, without mailing anything. You can use this
with B<-v> to get more complete data.
=item B<-e>
Editor to use.
=item B<-f>
File containing the body of the report. Use this to quickly send a
prepared message.
=item B<-F>
File to output the results to instead of sending as an email. Useful
particularly when running perlbug on a machine with no direct internet
connection.
=item B<-h>
Prints a brief summary of the options.
=item B<-ok>
Report successful build on this system to perl porters. Forces B<-S>
and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
prompts for a return address if it cannot guess it (for use with
B). Honors return address specified with B<-r>. You can use this
with B<-v> to get more complete data. Only makes a report if this
system is less than 60 days old.
=item B<-okay>
As B<-ok> except it will report on older systems.
=item B<-nok>
Report unsuccessful build on this system. Forces B<-C>. Forces and
supplies a value for B<-s>, then requires you to edit the report
and say what went wrong. Alternatively, a prepared report may be
supplied using B<-f>. Only prompts for a return address if it
cannot guess it (for use with B). Honors return address
specified with B<-r>. You can use this with B<-v> to get more
complete data. Only makes a report if this system is less than 60
days old.
=item B<-nokay>
As B<-nok> except it will report on older systems.
=item B<-r>
Your return address. The program will ask you to confirm its default
if you don't use this option.
=item B<-S>
Send without asking for confirmation.
=item B<-s>
Subject to include with the message. You will be prompted if you don't
supply one on the command line.
=item B<-t>
Test mode. The target address defaults to B.
=item B<-T>
Send a thank-you note instead of a bug report.
=item B<-v>
Include verbose configuration data in the report.
=back
=head1 AUTHORS
Kenneth Albanowski (Ekjahds@kjahds.comE), subsequently
Itored by Gurusamy Sarathy (Egsar@activestate.comE),
Tom Christiansen (Etchrist@perl.comE), Nathan Torkington
(Egnat@frii.comE), Charles F. Randall (Ecfr@pobox.comE),
Mike Guy (Emjtg@cam.a.ukE), Dominic Dunlop
(Edomo@computer.orgE), Hugo van der Sanden (Ehv@crypt.org),
Jarkko Hietaniemi (Ejhi@iki.fiE), Chris Nandor
(Epudge@pobox.comE), Jon Orwant (Eorwant@media.mit.eduE,
Richard Foley (Erichard.foley@rfi.netE), and Jesse Vincent
(Ejesse@bestpractical.com).
=head1 SEE ALSO
perl(1), perldebug(1), perldiag(1), perlport(1), perltrap(1),
diff(1), patch(1), dbx(1), gdb(1)
=head1 BUGS
None known (guess what must have been used to report them?)
=cut