Since a properly created package has a MANIFEST file, you could extract just that, then use Module::Locate to test if the modules in the package have been installed.

Disclaimer: Not tested. YMMV

#!perl use strict; use warnings; use Archive::Tar; use Module::Locate qw/ locate /; my $tar = Archive::Tar->new; $tar->read('origin.tgz', COMPRESS_GZIP, {filter => 'MANIFEST'}); my @files = split /[\r\n]/, $tar->get_content( 'MANIFEST' ); my @modfiles = grep s|lib/||, @files; my @modules = map s|/|::|, @modfiles; for (@modules) { my $p = locate($_); if ($p) { print "Found '$_' at '$p'\n"; } else { print "Not installed: '$_'\n"; } }

In reply to Re: find module name from the module archive by RonW
in thread find module name from the module archive by Lotus1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.