summaryrefslogtreecommitdiff
path: root/pod/perlmodlib.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-03-19 09:20:22 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-03-19 09:20:22 +0000
commit6175e92675be1342fe51e34be66eb32d50cd8c0b (patch)
treec4c1e32546ebbe26100263579261519cb2172194 /pod/perlmodlib.pod
parent227e8dd41da683de6280c9d2acd3b6b29fd52832 (diff)
downloadperl-6175e92675be1342fe51e34be66eb32d50cd8c0b.tar.gz
mention how to look up perllocal.pod (from Michael G Schwern)
p4raw-id: //depot/perl@5827
Diffstat (limited to 'pod/perlmodlib.pod')
-rw-r--r--pod/perlmodlib.pod15
1 files changed, 10 insertions, 5 deletions
diff --git a/pod/perlmodlib.pod b/pod/perlmodlib.pod
index c1f4aca6be..b42a2d881c 100644
--- a/pod/perlmodlib.pod
+++ b/pod/perlmodlib.pod
@@ -802,17 +802,22 @@ By-name interface to Perl's built-in getpw*() functions
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
-They should all have their own documentation installed and accessible
-via your system man(1) command. If you do not have a B<find>
+To get a log of all module distributions which have been installed
+since perl was installed, just do:
+
+ % perldoc perllocal
+
+Modules should all have their own documentation installed and accessible
+via your system man(1) command, or via the C<perldoc> program. If you do
+not have a B<find>
program, you can use the Perl B<find2perl> program instead, which
generates Perl code as output you can run through perl. If you
have a B<man> program but it doesn't find your modules, you'll have
-to fix your manpath. See L<perl> for details. If you have no
-system B<man> command, you might try the B<perldoc> program.
+to fix your manpath. See L<perl> for details.
=head2 Extension Modules