How to find what perl modules are available for use ?

TS6.7.2, Solaris10

How to find out what perl modules are available for use in a code. How can I do that ? I tried "perldoc perldoc", but it doesnt give the list of all modules installed.

Is there a command or a way to find out what modules are installed on the server ?

thanks

Find more posts tagged with

Comments

Adam Stoller

TS6.7.2, Solaris10

How to find out what perl modules are available for use in a code. How can I do that ? I tried "perldoc perldoc", but it doesnt give the list of all modules installed.

Is there a command or a way to find out what modules are installed on the server ?

thanks

Sure - look through the IWHOME/iw-perl directory tree.
Or run cpan and at the prompt do the following:

cpan[1]> m

(that's a lowercase 'M' in case it isn't clear)
Hit return, and wait a bit and you should get a full listing of every module on the system. Note:

$/i) { $self->{aux}{count}++; (my $modname = $fname) =~ s|^.*?/lib/||; $modname =~ s|/|:gsm; push(@{$self->{aux}{mods}}, $modname); } return 1;} and run it.On my 672SP1 Windows machine, the above script shows me as having 2169 modules

nirjari

when I did "perldoc perllocal", it did return a list of modules. So will cpan[1]>1 will return the same rame result ? Or is this command returns different list ?

thanks

nipper

when I did "perldoc perllocal", it did return a list of modules. So will cpan[1]>1 will return the same rame result ? Or is this command returns different list ?

thanks

In the time it will take for you to wait for an answer, you could run that and find out yourself

Adam Stoller

when I did "perldoc perllocal", it did return a list of modules. So will cpan[1]>1 will return the same rame result ? Or is this command returns different list ?

thanks

I don't think "perldoc perllocal" returns a complete list of all modules (now that I think about it - one should update the code I posted to cycle through the @INC paths to search instead of the more simplistic approach I took when I quickly wrote that code) - and the output appears to be date-sorted (if anything) which is probably nowhere as useful as being name-sorted IMO.

ISCBorisB

I don't think "perldoc perllocal" returns a complete list of all modules (now that I think about it - one should update the code I posted to cycle through the @INC paths to search instead of the more simplistic approach I took when I quickly wrote that code) - and the output appears to be date-sorted (if anything) which is probably nowhere as useful as being name-sorted IMO.

Why not simply something like

ls -lR `iwgethome`/iw-perl/*.pm

at least for the first rough look?

Adam Stoller

Why not simply something like

ls -lR `iwgethome`/iw-perl/*.pm

at least for the first rough look?

I don't believe that command, as written, would work - though if you're looking for the quick-and-dirty Unix style:

find `iwgethome`/iw-perl -name "*.pm"

would probably do the trick.
The Perl script was just something that was a bit more portable, both across platforms, and across Perl installations (i.e., not just for iwperl) - and it formats the output in terms of module name format rather than path format.

ISCBorisB

I don't believe that command [..]would work

I must have been out of my mind - the price to pay for working in wintel for far too long and typing with the
brain switched off! Of course it won't work, wildcart is evaluated by the shell so -R switch won't help etc..

Thanks Adam