4 use File::Basename qw(&basename &dirname);
7 # List explicitly here the variables you want Configure to
8 # generate. Metaconfig only looks for shell variables, so you
9 # have to mention them as if they were shell variables, not
10 # %Config entries. Thus you write
12 # to ensure Configure will look for $Config{startperl}.
15 # This forces PL files to create target in same directory as PL file.
16 # This is so that make depend always knows where to find PL derivatives.
19 $file = basename($0, '.PL');
20 $file .= '.com' if $^O eq 'VMS';
22 open OUT, ">$file" or die "Can't create $file: $!";
24 # extract patchlevel.h information
26 open PATCH_LEVEL, "<../patchlevel.h" or die "Can't open patchlevel.h: $!";
28 my $patchlevel_date = (stat PATCH_LEVEL)[9];
30 while (<PATCH_LEVEL>) {
31 last if $_ =~ /^\s*static\s+char.*?local_patches\[\]\s*=\s*{\s*$/;
35 while (<PATCH_LEVEL>) {
41 push @patches, $_ unless $_ eq 'NULL';
43 my $patch_desc = "'" . join("',\n '", @patches) . "'";
44 my $patch_tags = join "", map /(\S+)/ ? "+$1 " : (), @patches;
48 # TO DO (prehaps): store/embed $Config::config_sh into perlbug. When perlbug is
49 # used, compare $Config::config_sh with the stored version. If they differ then
50 # append a list of individual differences to the bug report.
53 print "Extracting $file (with variable substitutions)\n";
55 # In this section, perl variables will be expanded during extraction.
56 # You can use $Config{...} to use Configure variables.
58 print OUT <<"!GROK!THIS!";
60 eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
61 if \$running_under_some_shell;
63 my \$config_tag1 = '$] - $Config{cf_time}';
65 my \$patchlevel_date = $patchlevel_date;
66 my \$patch_tags = '$patch_tags';
72 # In the following, perl variables are not expanded during extraction.
74 print OUT <<'!NO!SUBS!';
83 eval "use Mail::Send;";
84 $::HaveSend = ($@ eq "");
85 eval "use Mail::Util;";
86 $::HaveUtil = ($@ eq "");
91 # Changed in 1.06 to skip Mail::Send and Mail::Util if not available.
92 # Changed in 1.07 to see more sendmail execs, and added pipe output.
93 # Changed in 1.08 to use correct address for sendmail.
94 # Changed in 1.09 to close the REP file before calling it up in the editor.
95 # Also removed some old comments duplicated elsewhere.
96 # Changed in 1.10 to run under VMS without Mail::Send; also fixed
97 # temp filename generation.
98 # Changed in 1.11 to clean up some text and removed Mail::Send deactivator.
99 # Changed in 1.12 to check for editor errors, make save/send distinction
100 # clearer and add $ENV{REPLYTO}.
101 # Changed in 1.13 to hopefully make it more difficult to accidentally
103 # Changed in 1.14 to make the prompts a little more clear on providing
104 # helpful information. Also let file read fail gracefully.
105 # Changed in 1.15 to add warnings to stop people using perlbug for non-bugs.
106 # Also report selected environment variables.
107 # Changed in 1.16 to include @INC, and allow user to re-edit if no changes.
108 # Changed in 1.17 Win32 support added. GSAR 97-04-12
109 # Changed in 1.18 add '-ok' option for reporting build success. CFR 97-06-18
110 # Changed in 1.19 '-ok' default not '-v'
111 # add local patch information
112 # warn on '-ok' if this is an old system; add '-okay'
113 # Changed in 1.20 Added patchlevel.h reading and version/config checks
114 # Changed in 1.21 Added '-nok' for reporting build failure DFD 98-05-05
115 # Changed in 1.22 Heavy reformatting & minor bugfixes HVDS 98-05-10
116 # Changed in 1.23 Restore -ok(ay): say 'success'; don't prompt
117 # Changed in 1.24 Added '-F<file>' to save report HVDS 98-07-01
119 # TODO: - Allow the user to re-name the file on mail failure, and
120 # make sure failure (transmission-wise) of Mail::Send is
124 my( $file, $usefile, $cc, $address, $perlbug, $testaddress, $filename,
125 $subject, $from, $verbose, $ed, $outfile,
126 $fh, $me, $Is_MSWin32, $Is_VMS, $msg, $body, $andcc, %REP, $ok);
128 my $config_tag2 = "$] - $Config{cf_time}";
132 if ($::opt_h) { Help(); exit; }
133 if ($::opt_d) { Dump(*STDOUT); exit; }
136 Please use perlbug interactively. If you want to
137 include a file, you can use the -f switch.
141 if (!-t STDOUT && !$outfile) { Dump(*STDOUT); exit; }
144 Edit() unless $usefile || ($ok and not $::opt_n);
151 # -------- Setup --------
153 $Is_MSWin32 = $^O eq 'MSWin32';
154 $Is_VMS = $^O eq 'VMS';
156 getopts("dhva:s:b:f:F:r:e:SCc:to:n:");
158 # This comment is needed to notify metaconfig that we are
159 # using the $perladmin, $cf_by, and $cf_time definitions.
161 # -------- Configuration ---------
164 $perlbug = 'perlbug@perl.com';
167 $testaddress = 'perlbug-test@perl.com';
170 $address = $::opt_a || ($::opt_t ? $testaddress : $perlbug);
172 # Users address, used in message and in Reply-To header
173 $from = $::opt_r || "";
175 # Include verbose configuration information
176 $verbose = $::opt_v || 0;
178 # Subject of bug-report message
179 $subject = $::opt_s || "";
182 $usefile = ($::opt_f || 0);
184 # File to send as report
185 $file = $::opt_f || "";
188 $outfile = $::opt_F || "";
191 $body = $::opt_b || "";
194 $ed = $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT}
195 || ($Is_VMS && "edit/tpu")
196 || ($Is_MSWin32 && "notepad")
199 # Not OK - provide build failure template by finessing OK report
201 if (substr($::opt_n, 0, 2) eq 'ok' ) {
202 $::opt_o = substr($::opt_n, 1);
209 # OK - send "OK" report for build on this system
212 if ($::opt_o eq 'k' or $::opt_o eq 'kay') {
213 my $age = time - $patchlevel_date;
214 if ($::opt_o eq 'k' and $age > 60 * 24 * 60 * 60 ) {
215 my $date = localtime $patchlevel_date;
217 "perlbug -ok" and "perlbug -nok" do not report on Perl versions which
218 are more than 60 days old. This Perl version was constructed on
219 $date. If you really want to report this, use
220 "perlbug -okay" or "perlbug -nokay".
224 # force these options
226 $::opt_S = 1; # don't prompt for send
227 $::opt_b = 1; # we have a body
228 $body = "Perl reported to build OK on this system.\n";
230 $::opt_C = 1; # don't send a copy to the local admin
231 $::opt_s = 1; # we have a subject line
232 $subject = ($::opt_n ? 'Not ' : '')
233 . "OK: perl $] ${patch_tags}on"
234 ." $::Config{'archname'} $::Config{'osvers'} $subject";
242 # Possible administrator addresses, in order of confidence
243 # (Note that cf_email is not mentioned to metaconfig, since
244 # we don't really want it. We'll just take it if we have to.)
246 # This has to be after the $ok stuff above because of the way
247 # that $::opt_C is forced.
248 $cc = $::opt_C ? "" : (
249 $::opt_c || $::Config{'perladmin'}
250 || $::Config{'cf_email'} || $::Config{'cf_by'}
254 $me = $Is_MSWin32 ? $ENV{'USERNAME'}
255 : $^O eq 'os2' ? $ENV{'USER'} || $ENV{'LOGNAME'}
256 : eval { getpwuid($<) }; # May be missing
258 $from = $::Config{'cf_email'}
259 if !$from && $::Config{'cf_email'} && $::Config{'cf_by'} && $me &&
260 ($me eq $::Config{'cf_by'});
264 # Explain what perlbug is
267 This program provides an easy way to create a message reporting a bug
268 in perl, and e-mail it to $address. It is *NOT* intended for
269 sending test messages or simply verifying that perl works, *NOR* is it
270 intended for reporting bugs in third-party perl modules. It is *ONLY*
271 a means of reporting verifiable problems with the core perl distribution,
272 and any solutions to such problems, to the people who maintain perl.
274 If you're just looking for help with perl, try posting to the Usenet
275 newsgroup comp.lang.perl.misc. If you're looking for help with using
276 perl with CGI, try posting to comp.infosystems.www.programming.cgi.
280 # Prompt for subject of message, if needed
283 First of all, please provide a subject for the
284 message. It should be a concise description of
285 the bug or problem. "perl bug" or "perl problem"
286 is not a concise description.
292 while ($subject !~ /\S/) {
293 print "\nPlease enter a subject: ";
302 # Prompt for return address, if needed
304 # Try and guess return address
307 $guess = $ENV{'REPLY-TO'} || $ENV{'REPLYTO'} || '';
311 $domain = Mail::Util::maildomain();
312 } elsif ($Is_MSWin32) {
313 $domain = $ENV{'USERDOMAIN'};
315 require Sys::Hostname;
316 $domain = Sys::Hostname::hostname();
319 if ($Is_VMS && !$::Config{'d_socket'}) {
320 $guess = "$domain\:\:$me";
322 $guess = "$me\@$domain" if $domain;
330 Your e-mail address will be useful if you need to be contacted. If the
331 default shown is not your full internet e-mail address, please correct it.
336 So that you may be contacted if necessary, please enter
337 your full internet e-mail address here.
346 print "Your address [$guess]: ";
349 $from = $guess if $from eq '';
353 if ($from eq $cc or $me eq $cc) {
354 # Try not to copy ourselves
358 # Prompt for administrator address, unless an override was given
359 if( !$::opt_C and !$::opt_c ) {
361 A copy of this report can be sent to your local
362 perl administrator. If the address is wrong, please
363 correct it, or enter 'none' or 'yourself' to not send
366 print "Local perl administrator [$cc]: ";
367 my $entry = scalar <>;
372 $cc = '' if $me eq $cc;
376 $cc = '' if $cc =~ /^(none|yourself|me|myself|ourselves)$/i;
377 $andcc = " and $cc" if $cc;
379 # Prompt for editor, if no override is given
381 unless ($::opt_e || $::opt_f || $::opt_b) {
383 Now you need to supply the bug report. Try to make
384 the report concise but descriptive. Include any
385 relevant detail. If you are reporting something
386 that does not work as you think it should, please
387 try to include example of both the actual
388 result, and what you expected.
390 Some information about your local
391 perl configuration will automatically be included
392 at the end of the report. If you are using any
393 unusual version of perl, please try and confirm
394 exactly which versions are relevant.
396 You will probably want to use an editor to enter
397 the report. If "$ed" is the editor you want
398 to use, then just press Enter, otherwise type in
399 the name of the editor you would like to use.
401 If you would like to use a prepared file, type
402 "file", and you will be asked for the filename.
404 print "Editor [$ed]: ";
405 my $entry =scalar <>;
409 if ($entry eq "file") {
411 } elsif ($entry ne "") {
416 # Generate scratch file to edit report in
417 $filename = filename();
419 # Prompt for file to read report from, if needed
420 if ($usefile and !$file) {
423 What is the name of the file that contains your report?
426 my $entry = scalar <>;
431 No filename? I'll let you go back and choose an editor again.
436 unless (-f $entry and -r $entry) {
438 I'm sorry, but I can't read from `$entry'. Maybe you mistyped the name of
439 the file? If you don't want to send a file, just enter a blank line and you
440 can get back to the editor selection.
448 open(REP,">$filename");
449 my $reptype = !$ok ? "bug" : $::opt_n ? "build failure" : "success";
452 This is a $reptype report for perl from $from,
453 generated with the help of perlbug $Version running under perl $].
461 or die "Unable to read report file from `$file': $!\n";
469 -----------------------------------------------------------------
470 [Please enter your report here]
474 [Please do not change anything below this line]
475 -----------------------------------------------------------------
481 # read in the report template once so that
482 # we can track whether the user does any editing.
483 # yes, *all* whitespace is ignored.
484 open(REP, "<$filename");
496 print REP "This perlbug was built using Perl $config_tag1\n",
497 "It is being executed now by Perl $config_tag2.\n\n"
498 if $config_tag2 ne $config_tag1;
501 Site configuration information for perl $]:
504 if ($::Config{cf_by} and $::Config{cf_time}) {
505 print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
507 print OUT Config::myconfig;
510 print OUT join "\n ", "Locally applied patches:", @patches;
526 Environment for perl $]:
529 (qw(PATH LD_LIBRARY_PATH LANG PERL_BADLANG SHELL HOME LOGDIR),
530 grep /^(?:PERL|LC_)/, keys %ENV)
533 exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
537 print OUT "\nComplete configuration data for perl $]:\n\n";
539 foreach (sort keys %::Config) {
540 $value = $::Config{$_};
542 print OUT "$_='$value'\n";
549 if ($usefile || $body) {
551 Please make sure that the name of the editor you want to use is correct.
553 print "Editor [$ed]: ";
554 my $entry =scalar <>;
556 $ed = $entry unless $entry eq '';
560 my $sts = system("$ed $filename");
563 The editor you chose (`$ed') could apparently not be run!
564 Did you mistype the name of your editor? If so, please
565 correct it here, otherwise just press Enter.
567 print "Editor [$ed]: ";
568 my $entry =scalar <>;
576 You may want to save your report to a file, so you can edit and mail it
582 return if ($ok and not $::opt_n) || $body;
583 # Check that we have a report that has some, eh, report in it.
586 open(REP, "<$filename");
587 # a strange way to check whether any significant editing
588 # have been done: check whether any new non-empty lines
589 # have been added. Yes, the below code ignores *any* space
593 $unseen++ if $_ ne '' and not exists $REP{$_};
596 while ($unseen == 0) {
598 I am sorry but it looks like you did not report anything.
600 print "Action (Retry Edit/Cancel) ";
601 my ($action) = scalar(<>);
602 if ($action =~ /^[re]/i) { # <R>etry <E>dit
604 } elsif ($action =~ /^[cq]/i) { # <C>ancel, <Q>uit
611 1 while unlink($filename); # remove all versions under VMS
612 print "\nCancelling.\n";
617 # Report is done, prompt for further action
621 Now that you have completed your report, would you like to send
622 the message to $address$andcc, display the message on
623 the screen, re-edit it, or cancel without sending anything?
624 You may also save the message as a file to mail at another time.
626 print "Action (Send/Display/Edit/Cancel/Save to File): ";
627 my $action = scalar <>;
630 if ($action =~ /^(f|sa)/i) { # <F>ile/<Sa>ve
631 print "\n\nName of file to save message in [perlbug.rep]: ";
632 my $file = scalar <>;
634 $file = "perlbug.rep" if $file eq "";
636 open(FILE, ">$file");
637 open(REP, "<$filename");
638 print FILE "To: $address\nSubject: $subject\n";
639 print FILE "Cc: $cc\n" if $cc;
640 print FILE "Reply-To: $from\n" if $from;
642 while (<REP>) { print FILE }
646 print "\nMessage saved in `$file'.\n";
648 } elsif ($action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
649 # Display the message
650 open(REP, "<$filename");
651 while (<REP>) { print $_ }
653 } elsif ($action =~ /^se/i) { # <S>end
655 print "Are you certain you want to send this message?\n"
656 . 'Please type "yes" if you are: ';
657 my $reply = scalar <STDIN>;
659 if ($reply eq "yes") {
663 That wasn't a clear "yes", so I won't send your message. If you are sure
664 your message should be sent, type in "yes" (without the quotes) at the
668 } elsif ($action =~ /^[er]/i) { # <E>dit, <R>e-edit
671 } elsif ($action =~ /^[qc]/i) { # <C>ancel, <Q>uit
673 } elsif ($action =~ /^s/) {
675 I'm sorry, but I didn't understand that. Please type "send" or "save".
683 # Message has been accepted for transmission -- Send the message
685 open SENDMAIL, ">$outfile" or die "Couldn't open '$outfile': $!\n";
689 $msg = new Mail::Send Subject => $subject, To => $address;
690 $msg->cc($cc) if $cc;
691 $msg->add("Reply-To",$from) if $from;
694 open(REP, "<$filename");
695 while (<REP>) { print $fh $_ }
699 print "\nMessage sent.\n";
701 if ( ($address =~ /@/ and $address !~ /^\w+%"/) or
702 ($cc =~ /@/ and $cc !~ /^\w+%"/) ) {
704 foreach (qw[ IN MX SMTP UCX PONY WINS ], '') {
705 $prefix = "$_%", last if $ENV{"MAIL\$PROTOCOL_$_"};
707 $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
708 $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
710 $subject =~ s/"/""/g; $address =~ s/"/""/g; $cc =~ s/"/""/g;
711 my $sts = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
715 (leaving bug report in $filename): $sts
720 for (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail)) {
721 $sendmail = $_, last if -e $_;
723 if ($^O eq 'os2' and $sendmail eq "") {
724 my $path = $ENV{PATH};
726 my @path = split /$Config{'path_sep'}/, $path;
728 $sendmail = "$_/sendmail", last if -e "$_/sendmail";
729 $sendmail = "$_/sendmail.exe", last if -e "$_/sendmail.exe";
733 paraprint(<<"EOF"), die "\n" if $sendmail eq "";
734 I am terribly sorry, but I cannot find sendmail, or a close equivalent, and
735 the perl package Mail::Send has not been installed, so I can't send your bug
736 report. We apologize for the inconvenience.
738 So you may attempt to find some way of sending your message, it has
739 been left in the file `$filename'.
741 open(SENDMAIL, "|$sendmail -t") || die "'|$sendmail -t' failed: $!";
743 print SENDMAIL "To: $address\n";
744 print SENDMAIL "Subject: $subject\n";
745 print SENDMAIL "Cc: $cc\n" if $cc;
746 print SENDMAIL "Reply-To: $from\n" if $from;
747 print SENDMAIL "\n\n";
748 open(REP, "<$filename");
749 while (<REP>) { print SENDMAIL $_ }
752 if (close(SENDMAIL)) {
753 printf "\nMessage %s.\n", $outfile ? "saved" : "sent";
755 warn "\nSendmail returned status '", $? >> 8, "'\n";
758 1 while unlink($filename); # remove all versions under VMS
764 A program to help generate bug reports about perl5, and mail them.
765 It is designed to be used interactively. Normally no arguments will
769 $0 [-v] [-a address] [-s subject] [-b body | -f inpufile ] [ -F outputfile ]
770 [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
771 $0 [-v] [-r returnaddress] [-ok | -okay | -nok | -nokay]
773 Simplest usage: run "$0", and follow the prompts.
777 -v Include Verbose configuration data in the report
778 -f File containing the body of the report. Use this to
779 quickly send a prepared message.
780 -F File to output the resulting mail message to, instead of mailing.
781 -S Send without asking for confirmation.
782 -a Address to send the report to. Defaults to `$address'.
783 -c Address to send copy of report to. Defaults to `$cc'.
784 -C Don't send copy to administrator.
785 -s Subject to include with the message. You will be prompted
786 if you don't supply one on the command line.
787 -b Body of the report. If not included on the command line, or
788 in a file with -f, you will get a chance to edit the message.
789 -r Your return address. The program will ask you to confirm
790 this if you don't give it here.
792 -t Test mode. The target address defaults to `$testaddress'.
793 -d Data mode (the default if you redirect or pipe output.)
794 This prints out your configuration data, without mailing
795 anything. You can use this with -v to get more complete data.
796 -ok Report successful build on this system to perl porters
797 (use alone or with -v). Only use -ok if *everything* was ok:
798 if there were *any* problems at all, use -nok.
799 -okay As -ok but allow report from old builds.
800 -nok Report unsuccessful build on this system to perl porters
801 (use alone or with -v). You must describe what went wrong
802 in the body of the report which you will be asked to edit.
803 -nokay As -nok but allow report from old builds.
804 -h Print this help message.
810 my $dir = $Is_VMS ? 'sys$scratch:'
811 : ($Is_MSWin32 && $ENV{'TEMP'}) ? $ENV{'TEMP'}
813 $filename = "bugrep0$$";
814 $dir .= "\\" if $Is_MSWin32 and $dir !~ m|[\\/]$|;
815 $filename++ while -e "$dir$filename";
816 $filename = "$dir$filename";
820 my @paragraphs = split /\n{2,}/, "@_";
822 for (@paragraphs) { # implicit local $_
830 ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
838 perlbug - how to submit bug reports on Perl
842 B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
843 S<[ B<-b> I<body> | B<-f> I<inputfile> ]> S<[ B<-F> I<outputfile> ]>
844 S<[ B<-r> I<returnaddress> ]>
845 S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
846 S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-h> ]>
848 B<perlbug> S<[ B<-v> ]> S<[ B<-r> I<returnaddress> ]>
849 S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]>
853 A program to help generate bug reports about perl or the modules that
854 come with it, and mail them.
856 If you have found a bug with a non-standard port (one that was not part
857 of the I<standard distribution>), a binary distribution, or a
858 non-standard module (such as Tk, CGI, etc), then please see the
859 documentation that came with that distribution to determine the correct
860 place to report bugs.
862 C<perlbug> is designed to be used interactively. Normally no arguments
863 will be needed. Simply run it, and follow the prompts.
865 If you are unable to run B<perlbug> (most likely because you don't have
866 a working setup to send mail that perlbug recognizes), you may have to
867 compose your own report, and email it to B<perlbug@perl.com>. You might
868 find the B<-d> option useful to get summary information in that case.
870 In any case, when reporting a bug, please make sure you have run through
875 =item What version of perl you are running?
877 Type C<perl -v> at the command line to find out.
879 =item Are you running the latest released version of perl?
881 Look at http://www.perl.com/ to find out. If it is not the latest
882 released version, get that one and see whether your bug has been
883 fixed. Note that bug reports about old versions of perl, especially
884 those prior to the 5.0 release, are likely to fall upon deaf ears.
885 You are on your own if you continue to use perl1 .. perl4.
887 =item Are you sure what you have is a bug?
889 A significant number of the bug reports we get turn out to be documented
890 features in perl. Make sure the behavior you are witnessing doesn't fall
891 under that category, by glancing through the documentation that comes
892 with perl (we'll admit this is no mean task, given the sheer volume of
893 it all, but at least have a look at the sections that I<seem> relevant).
895 Be aware of the familiar traps that perl programmers of various hues
896 fall into. See L<perltrap>.
898 Try to study the problem under the perl debugger, if necessary.
901 =item Do you have a proper test case?
903 The easier it is to reproduce your bug, the more likely it will be
904 fixed, because if no one can duplicate the problem, no one can fix it.
905 A good test case has most of these attributes: fewest possible number
906 of lines; few dependencies on external commands, modules, or
907 libraries; runs on most platforms unimpeded; and is self-documenting.
909 A good test case is almost always a good candidate to be on the perl
910 test suite. If you have the time, consider making your test case so
911 that it will readily fit into the standard test suite.
913 =item Can you describe the bug in plain English?
915 The easier it is to understand a reproducible bug, the more likely it
916 will be fixed. Anything you can provide by way of insight into the
917 problem helps a great deal. In other words, try to analyse the
918 problem to the extent you feel qualified and report your discoveries.
920 =item Can you fix the bug yourself?
922 A bug report which I<includes a patch to fix it> will almost
923 definitely be fixed. Use the C<diff> program to generate your patches
924 (C<diff> is being maintained by the GNU folks as part of the B<diffutils>
925 package, so you should be able to get it from any of the GNU software
926 repositories). If you do submit a patch, the cool-dude counter at
927 perlbug@perl.com will register you as a savior of the world. Your
928 patch may be returned with requests for changes, or requests for more
929 detailed explanations about your fix.
931 Here are some clues for creating quality patches: Use the B<-c> or
932 B<-u> switches to the diff program (to create a so-called context or
933 unified diff). Make sure the patch is not reversed (the first
934 argument to diff is typically the original file, the second argument
935 your changed file). Make sure you test your patch by applying it with
936 the C<patch> program before you send it on its way. Try to follow the
937 same style as the code you are trying to patch. Make sure your patch
938 really does work (C<make test>, if the thing you're patching supports
941 =item Can you use C<perlbug> to submit the report?
943 B<perlbug> will, amongst other things, ensure your report includes
944 crucial information about your version of perl. If C<perlbug> is unable
945 to mail your report after you have typed it in, you may have to compose
946 the message yourself, add the output produced by C<perlbug -d> and email
947 it to B<perlbug@perl.com>. If, for some reason, you cannot run
948 C<perlbug> at all on your system, be sure to include the entire output
949 produced by running C<perl -V> (note the uppercase V).
953 Having done your bit, please be prepared to wait, to be told the bug
954 is in your code, or even to get no reply at all. The perl maintainers
955 are busy folks, so if your problem is a small one or if it is difficult
956 to understand or already known, they may not respond with a personal reply.
957 If it is important to you that your bug be fixed, do monitor the
958 C<Changes> file in any development releases since the time you submitted
959 the bug, and encourage the maintainers with kind words (but never any
960 flames!). Feel free to resend your bug report if the next released
961 version of perl comes out and your bug is still present.
969 Address to send the report to. Defaults to `perlbug@perl.com'.
973 Body of the report. If not included on the command line, or
974 in a file with B<-f>, you will get a chance to edit the message.
978 Don't send copy to administrator.
982 Address to send copy of report to. Defaults to the address of the
983 local perl administrator (recorded when perl was built).
987 Data mode (the default if you redirect or pipe output). This prints out
988 your configuration data, without mailing anything. You can use this
989 with B<-v> to get more complete data.
997 File containing the body of the report. Use this to quickly send a
1002 File to output the results to instead of sending as an email. Useful
1003 particularly when running perlbug on a machine with no direct internet
1008 Prints a brief summary of the options.
1012 Report successful build on this system to perl porters. Forces B<-S>
1013 and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
1014 prompts for a return address if it cannot guess it (for use with
1015 B<make>). Honors return address specified with B<-r>. You can use this
1016 with B<-v> to get more complete data. Only makes a report if this
1017 system is less than 60 days old.
1021 As B<-ok> except it will report on older systems.
1025 Report unsuccessful build on this system. Forces B<-C>. Forces and
1026 supplies a value for B<-s>, then requires you to edit the report
1027 and say what went wrong. Alternatively, a prepared report may be
1028 supplied using B<-f>. Only prompts for a return address if it
1029 cannot guess it (for use with B<make>). Honors return address
1030 specified with B<-r>. You can use this with B<-v> to get more
1031 complete data. Only makes a report if this system is less than 60
1036 As B<-nok> except it will report on older systems.
1040 Your return address. The program will ask you to confirm its default
1041 if you don't use this option.
1045 Send without asking for confirmation.
1049 Subject to include with the message. You will be prompted if you don't
1050 supply one on the command line.
1054 Test mode. The target address defaults to `perlbug-test@perl.com'.
1058 Include verbose configuration data in the report.
1064 Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently I<doc>tored
1065 by Gurusamy Sarathy (E<lt>gsar@umich.eduE<gt>), Tom Christiansen
1066 (E<lt>tchrist@perl.comE<gt>), Nathan Torkington (E<lt>gnat@frii.comE<gt>),
1067 Charles F. Randall (E<lt>cfr@pobox.comE<gt>), Mike Guy
1068 (E<lt>mjtg@cam.a.ukE<gt>), Dominic Dunlop (E<lt>domo@computer.orgE<gt>)
1069 and Hugo van der Sanden (E<lt>hv@crypt0.demon.co.ukE<gt>).
1073 perl(1), perldebug(1), perltrap(1), diff(1), patch(1)
1077 None known (guess what must have been used to report them?)
1083 close OUT or die "Can't close $file: $!";
1084 chmod 0755, $file or die "Can't reset permissions for $file: $!\n";
1085 exec("$Config{'eunicefix'} $file") if $Config{'eunicefix'} ne ':';