llancet,

Usually, we wrote "#!/usr/bin/perl" at top of scripts, as perl is usually being installed there. However, if I provide a script within a CPAN package, there comes a problem: somebody (like me) may have another perl ....

When I install any Perl package (CPAN or other), I call it directly with:

  myperl -MCPAN -e 'install "..."'
[download]

What I refer to as 'myperl' is the exact Perl version where I want the package installed. Otherwise, it won't install to the correct directory structure. Obviously you could open the CPAN shell for multiple installs, etc.

But you may be worrying about something that just won't happen. When a user calls your CPAN package, Perl is already running so your shebang is not used. If your package isn't in the correct directory, it will fail at compile or runtime depending on how it's called (use/require/BEGIN).

If you are the sysadmin then you will install it where your clients can get to it!

Good Luck!