Thanks for the help, but I don't understand. Could you explain this more?

Are you saying that I can't rely upon ExtUtils::Installed because the .packlist files with the modules I download from CPAN might not be compliant, and therefore these modules won't show up when I look for them using my script?

If this is the case, is there another way to verify that this LONG list of modules is in fact correctly installed on my server?

For the halibut, I wrote:

#!/usr/local/bin/perl

use strict;
use warnings;
use Test::Tester;
use Test::PDF;
use ExtUtils::PkgConfig;
use ExtUtils::Depends;
use Cairo;
use Test::LongString;
use Text::Flow;
use Graphics::Primitive::Driver::Cairo;
use Math::Gradient;
use Set::Infinite;
use DateTime::Set;
use Algorithm::Diff;
use Text::Diff;
use Test::Differences;
use Color::Scheme;
use Class::Data::Inheritable;
use Class::Accessor::Fast;
use Module::Pluggable;
use Color::Library;
use Test::Number::Delta;
use MooseX::Aliases;
use Graphics::Color;
use Forest;
use Graphics::Primitive;
use MooseX::AttributeHelpers;
use JSON::Any;
use File::Path;
use File::NFSLock;
use IO::Dir;
use Path::Class;
use Carp::Clan;
use MooseX::Types;
use MooseX::Types::Path::Class;
use Test::TempDir;
use Test::NoWarnings;
use Test::Tester;
#use Test::Deep;
use String::RewritePrefix;
use MooseX::Storage;
use Math::Complex;
use Check::ISA;
use Hash::Util::FieldHash::Compat;
use Algorithm::C3;
use Class::C3;
use MRO::Compat;
use Scope::Guard;
use Devel::GlobalDestruction;
use Class::MOP;
use Try::Tiny;
use Moose;
use Task::Weaken;
use XSLoader;
use base;
use Variable::Magic;
use Data::OptList;
use Sub::Install;
use Params::Util;
use Sub::Exporter;
use B::Hooks::EndOfScope;
use Sub::Identify;
use Sub::Name;
use Package::Stash;
use namespace::clean;
use Tie::RefHash;
use Test::use::ok;
use Tie::ToObject;
use Data::Visitor;
use MooseX::Clone;
use Geometry::Primitive;
use ExtUtils::MakeMaker;
use Layout::Manager;
use Time::Local;
use List::MoreUtils;
use DateTime::Locale;
use File::Temp;
use Exporter;
use ExtUtils::ParseXS;
use Module::Build;
use Attribute::Handlers;
use ExtUtils::CBuilder;
use Params::Validate;
use Class::Singleton;
use DateTime::TimeZone;
use Test;
use Text::Wrap;
use Pod::Escapes;
use Pod::Simple;
use File::Spec;
use Pod::Man;
use Sub::Uplevel;
use Test::Exception;
use Test::Harness;
#use Test::More;
use Scalar::Util;
use DateTime;
use Chart::Clicker;

print "\nNo module import errors!\n\n";
exit;
[download]

But surely there is a better way to do this sort of thing?

Thanks!

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.