[PATCH pods 5.6RC2] Mention perllocal.pod in a few places

Lately I've been making use of perllocal alot, seeing the last time a
module was upgraded, useful for debugging.  This useful little file is
mentioned a total of one (1) time in the docs (in the
ExtUtils::Makemaker man page).

I figure it could use mentioning in a few other logical places, namely
perl.pod, perlmodlib and perlmodinstall.

The only sticky part about the whole affair is that since perllocal
isn't a man page, you have to be careful to make it clear that one
must use perldoc to read it.


--- pod/perl.pod        2000/03/19 03:15:21
+++ pod/perl.pod        2000/03/19 03:16:02
@@ -34,6 +34,7 @@
     perlmod            Perl modules: how they work
     perlmodlib         Perl modules: how to write and use
     perlmodinstall     Perl modules: how to install from CPAN
+    perllocal           Perl modules: what's installed (use perldoc)
     perlform           Perl formats
     perlunicode                Perl unicode support
     perllocale         Perl locale support
--- pod/perlmodlib.pod  2000/03/19 03:22:47
+++ pod/perlmodlib.pod  2000/03/19 03:24:52
@@ -802,9 +802,14 @@

 To find out I<all> modules installed on your system, including
 those without documentation or outside the standard release,
-jus tdo this:
+just do this:

     % find `perl -e 'print "@INC"'` -name '*.pm' -print
+
+To get a log of all modules which have been installed since perl was
+installed, just do:
+
+    % perldoc perllocal

 They should all have their own documentation installed and accessible
 via your system man(1) command.  If you do not have a B<find>
--- pod/perlmodinstall.pod      2000/03/19 03:25:00
+++ pod/perlmodinstall.pod      2000/03/19 03:28:44
@@ -91,11 +91,17 @@
 Make sure you have appropriate permissions to install the module
 in your Perl 5 library directory.  Often, you'll need to be root.

+A record of all module installations is kept.  To look at this, simply
+type:
+
+      perldoc perllocal
+
 That's all you need to do on Unix systems with dynamic linking.
 Most Unix systems have dynamic linking--if yours doesn't, or if for
 another reason you have a statically-linked perl, I<and> the
 module requires compilation, you'll need to build a new Perl binary
 that includes the module.  Again, you'll probably need to be root.
+

 =item *


-- 

Michael G. Schwern   <schwern@pobox.com>    http://www.pobox.com/~schwern/
Maybe they hooked you up with one of those ass-making magazines.
	 -- brian d. foy as misheard by Michael G Schwern

• [PATCH pods 5.6RC2] Mention perllocal.pod in a few places by Michael G Schwern