in reply to Loading Local Modules

As Joost has mentioned, you do have the option of PAR. This has been a godsend to me for transporting modules across Win32 boxes.

Depending upon your requirements, you can wrap what you need up in two ways.

Firstly as a PAR file containing the rogue module and all it's dependancies. Using pp (the Perl Packager) you can have:

pp -M XML::Simple -p xmlsimple

Alternative you can create a specific PAR file, but this will require you to delve into Module::ScanDeps a little and write a script like one I've recently written that can tar (Archive::Tar) or zip (Archive::Zip) the appropriate contents. Having created your PAR file you simple access it in your code as:

use PAR 'xmlsimple.par';

Secondly as an EXE file that runs as if you'd called your main script. Again using pp:

pp -o myscript.exe myscript.pl
which will wrap up the script with all it's dependancies and allow you to deploy as if a single script.

PAR and it's additional scripts are one of the most useful bundles you'll find on CPAN, when it comes to deploying your Perl applications.

--
Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/