Then you just use ExtUtils::Installed (you could use File::Find, but why go through the trouble when somebody already done it)

use ExtUtils::Installed;
my $inst = ExtUtils::Installed->new();
print "$_\n" for $inst->files('CGI');

=head1 on my machine, I get

    C:\Perl\lib\CGI\Util.pm
    C:\Perl\lib\CGI\Cookie.pm
    C:\Perl\lib\CGI.pm
    C:\Perl\lib\CGI\Push.pm
    C:\Perl\lib\CGI\Pretty.pm
    C:\Perl\lib\CGI\Fast.pm
    C:\Perl\lib\CGI\Carp.pm
    C:\Perl\lib\CGI\Switch.pm
    C:\Perl\lib\CGI\Apache.pm

=cut

# and now for the "deletion" part
print "unlinking ", unlink( $inst->files('CGI') );
[download]

Hmm, works just fine for me on various perls/systems, what exactly did you try, and what version of ExtUtils::Packlist/ExtUtils::Installed do you have?

How did you install Image::Magick?

I have used CPAN to install modules and tested this, and it all works out as expected. I suspect one of the ExtUtils modules you're using is messed up. Seeing how you're still getting a file list, a workaround is easy (use File::Find to locate those files in @INC and acquire absolute paths).

____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.

I looked into it some further using the following:

#!/usr/bin/perl -w
use strict;
use ExtUtils::Installed;
my $inst = ExtUtils::Installed->new();
print map "$_\n", @ARGV
        ? map $inst->files($_), @ARGV
        : $inst->modules();
__END__
[download]

I got the same pathless reply for any module I checked - bar Perl itself. All additional modules were installed using CPAN. In reply to your requests:
Read more... (3 kB)

Makeshifts last the longest.

Hmm. On my 5.6.1 it looks like this:

Magick.so
Magick.pm
autosplit.ix
Magick.bs
Image::Magick.3
[download]

Not really suitable to feed it into unlink..

Makeshifts last the longest.

I don't believe there are any mechanisms available to completely uninstall a module (assuming it wasn't installed with a package management system like RPM). If you just want to make a module unavailable to scripts, just find and delete the Module.pm file.

I found at least one good reason to do this: if the code you are writing tests whether a module is available (through an eval { require Module;} and defaults to a less-than-optimal-but-acceptable behaviour if the eval returns an error. Then you need to test both cases, with and without the module. A workaround is to wrap the eval in a test controlled by an environment variable, so when testing you can pretend that the module was not here. This is not perfect (the module could be imported by an other part of yur code or by an other module) but it is usually the easiest way to "desinstall" a module.

In this situation I would simply modify my code to allow me to test both situations by only requiring the module if a certain flag was set (or unset). Then I could just flip the value of the flag whenever I wanted to test the other bit of code. Certainly easier than uninstalling/reinstalling modules.