use strict;
use warnings;
use Imager;
The script will load the module that way. If you wanted to keep your personal modules in a central place you could create a subdirectory called 'libs' (if this is a web project) off of your docroot and change the above syntax to:
use libs/Imager.pm;
Again, that's assuming the script is in your docroot. Needless to say, you can have module files anywhere as long as the script can find them. I got the file to load but since I hadn't installed the complete package (Imager::Colorer, et al) it failed when I attempted to create a blank image using the sample script on the CPAN page.
Unfortunately there seems to be no Windows port so you would need the Cgwin package (*nix utilities for Windows) and have to download and 'make', 'make install' the Imager package manually. It does look cool though, having used ImageMagick in the past.
-ben
I have apache installed and have ActivePerl-5.8.6.811-MSWin32-x86-122208.msi sitting on my machine. Will this build automatically configure the connection with the server?