information about your perl, which may help us track down problems far
more quickly. But first you should read the advice in this file,
carefully re-read the error message and check the relevant manual pages
-on your system, as these may help you find an immediate solution. If
-you are not sure whether what you are seeing is a bug, you can send a
-message describing the problem to the comp.lang.perl.misc newsgroup to
-get advice.
+on your system, as these may help you find an immediate solution.
+Once you've exhausted the documentation, please report bugs to us using
+the 'perlbug' tool.
The perlbug tool is installed along with perl, so after you have
completed C<make install> it should be possible to run it with plain
=head1 Reporting Bugs
-If you find what you think is a bug, you might check the articles recently
-posted to the comp.lang.perl.misc newsgroup and the perl bug database at
-L<https://rt.perl.org/> . There may also be information at
+If you find what you think is a bug, you might check the perl bug database
+at L<https://rt.perl.org/> . There may also be information at
L<http://www.perl.org/> , the Perl Home Page.
If you believe you have an unreported bug, please run the L<perlbug> program
=head1 Help Save the World
You should definitely announce your patch on the perl5-porters list.
-You should also consider announcing your patch on
-comp.lang.perl.announce, though you should make it quite clear that a
-subversion is not a production release, and be prepared to deal with
-people who will not read your disclaimer.
=head1 Todo
正體中文版的歐萊禮 Perl 書藉
-=item L<http://groups.google.com/groups?q=tw.bbs.comp.lang.perl>
-
-臺灣 Perl 連線討論區 (也就是各大 BBS 的 Perl 連線版)
-
=back
=head2 Perl 使用者集會
# This script is designed to provide a handy summary of the configuration
# information being used to build perl. This is especially useful if you
-# are requesting help from comp.lang.perl.misc on usenet or via mail.
+# are requesting help online or via email.
# Note that the text lines /^Summary of/ .. /^\s*$/ are copied into Config.pm.
cat <<'!NO!SUBS!'
L<http://lists.perl.org>, check the particular website for that project.
Most mailing lists are archived at L<http://nntp.perl.org/>.
-There are also plenty of Perl related newsgroups located under
-C<comp.lang.perl.*>.
-
=head2 IRC
The Perl community has a rather large IRC presence. For starters, it has its
=head1 Reporting Bugs
-If you find what you think is a bug, you might check the articles recently
-posted to the comp.lang.perl.misc newsgroup and the perl bug database at
-L<https://rt.perl.org/> . There may also be information at
+If you find what you think is a bug, you might check the perl bug database
+at L<https://rt.perl.org/> . There may also be information at
L<http://www.perl.org/> , the Perl Home Page.
If you believe you have an unreported bug, please run the L<perlbug> program
don't send me mail asking for help on how to install your modules.
There are too many modules, and too few Orwants, for me to be able to
answer or even acknowledge all your questions. Contact the module
-author instead, or post to comp.lang.perl.modules, or ask someone
-familiar with Perl on your operating system.
+author instead, ask someone familiar with Perl on your operating
+system, or if all else fails, file a ticket at http://rt.cpan.org/.
=head1 AUTHOR
How to release and distribute a module.
-It's good idea to post an announcement of the availability of your
-module (or the module itself if small) to the comp.lang.perl.announce
-Usenet newsgroup. This will at least ensure very wide once-off
-distribution.
+If possible, register the module with CPAN. Follow the instructions
+and links on:
-If possible, register the module with CPAN. You should
-include details of its location in your announcement.
-
-Some notes about ftp archives: Please use a long descriptive file
-name that includes the version number. Most incoming directories
-will not be readable/listable, i.e., you won't be able to see your
-file after uploading it. Remember to send your email notification
-message as soon as possible after uploading else your file may get
-deleted automatically. Allow time for the file to be processed
-and/or check the file has been processed before announcing its
-location.
-
-FTP Archives for Perl Modules:
-
-Follow the instructions and links on:
-
- http://www.cpan.org/modules/00modlist.long.html
http://www.cpan.org/modules/04pause.html
-or upload to one of these sites:
+and upload to:
- https://pause.kbx.de/pause/
http://pause.perl.org/
-and notify <modules@perl.org>.
+and notify <modules@perl.org>. This will allow anyone to install
+your module using the C<cpan> tool distributed with Perl.
By using the WWW interface you can ask the Upload Server to mirror
your modules from your ftp or WWW site into your own directory on
CPAN!
-Please remember to send me an updated entry for the Module list!
-
=item *
Take care when changing a released module.
You might love it. You might feel that everyone else needs it. But there
might not actually be any real demand for it out there. If you're unsure
-about the demand your module will have, consider sending out feelers
-on the C<comp.lang.perl.modules> newsgroup, or as a last resort, ask the
-modules list at C<modules@perl.org>. Remember that this is a closed list
-with a very long turn-around time - be prepared to wait a good while for
-a response from them.
+about the demand your module will have, consider asking the
+C<module-authors@perl.org> mailing list (send an email to
+C<module-authors-subscribe@perl.org> to subscribe; see
+L<http://lists.perl.org/list/module-authors.html> for more information
+and a link to the archives).
=item Choose a name
Namespace" on PAUSE. Once registered, your module will appear in the
by-module and by-category listings on CPAN.
-=item Announce to clpa
-
-If you have a burning desire to tell the world about your release, post
-an announcement to the moderated C<comp.lang.perl.announce> newsgroup.
-
=item Fix bugs!
Once you start accumulating users, they'll send you bug reports. If
$! # This script is designed to provide a handy summary of the configuration
$! # information being used to build perl. This is especially useful if you
-$! # are requesting help from comp.lang.perl.misc on usenet or via mail.
+$! # are requesting help online or via email.
$! DCL-ified by Peter Prymmer <pvhp@lns62.lns.cornell.edu> 22-DEC-1995
$! DCL usage (choose one):
https://perl5.git.perl.org / perl5.git / commitdiff