I'm not sure if this will help or not, but I work in a similar enviornment, but have root access to the dev servers.

There's at least 2 way's around this delema:

1. Install your perl local to your shell and modify your LD_LIBRARY_PATH to point to the extra libs (which you've also put local to your shell.

2. I've managed to get CPAN modules into production by packaging everything i need into an 'install' script that sysadmins have no clue what they are really installing. Long as they don't have to answer any questions during the install process they seem to let it fly without questioning it.

coreolyn Deviously Devoted Perl in the Enterprise Advocate