As mentioned, as long as you have access to the tools necessary to build the module, you can install it into your own private lib directory. CPAN style modules already have support for this in their Makefile.PL. To take advantage of it, use the PREFIX setting:

  [user@host modules]$ tar xzvf Module-1.0.0.tar.gz
  [user@host modules]$ cd Module-1.0.0  
  [user@host Module-1.0.0]$ perl Makefile.PL PREFIX=$HOME/mylib
  [user@host Module-1.0.0]$ make && make test && make install
  [user@host Module-1.0.0]$ make && make test && make install
  [user@host modules]$ rm -rf Module-1.0.0
[download]

Then (again, as mentioned) add a 'use lib' to your program:

#!/usr/bin/perl -T
use strict;
use warnings;
use lib '/home/user/mylib/lib/site_perl/5.6.0';
use Module;
...
[download]

Just remember that you have to have the 'use lib' statement before the 'use Module;' statement.

Updated: Based on other feedback, I'd like to clarify that this technique can be used on a local system to create the install (if the system is binary compatible with the remote system, then it should even work for XS based modules) and then recursivly copied (ncftp is great for this) to the remote system.

amelinda - Thanks for pointing out that I missed the ftp only access.