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!

.packlist files with the modules I download from CPAN might not be compliant,

ExtUtils::Installed

ExtUtils::Installed provides a standard way to find out what core and module files have been installed. It uses the information stored in .packlist files created during installation to provide this information. In addition it provides facilities to classify the installed files and to extract directory information from the .packlist files.

So, if you install with cpan/Makefile.PL... it will make .packlist when you install.

If you install with apt-get and other OS specific tools, often times they will not make .packlist files , as such they're broken tools.

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?

Does

• useing the module successfully
• checking that all the files listed in .packlist exist/compile
verify that the module is correctly installed?

I just let CPAN/CPANPLUS handle it