I would handle this either through operating system level package management tools (yum, apt, etc.), or through containerization, or through setting up a MiniCPAN or DarkPAN. And I've done all three of those for different situations. Your organization must have some way of keeping servers updated, and installing software on them.
However, Net::SSH is pure Perl. And every dependency it requires ships with Perl 5. You should be able to do one of two things (in order of preferability):
The first solution has the advantage that it's predictable and repeatable. So long as the module's maintainers don't add external dependencies, it will always work. And you can hold onto that tarball should you ever need to reinstall the same version. The second solution's advantage is that it lets you work with a clear-text source code, which is easy to copy and paste. Ok, there's a third alternative; you unpack the tarball on a build system, and then copy/paste each file in the distribution into a build directory on the target box. That seems like too much work.
If your server can be hit over SSH, then you have scp or sftp, probably. Establishing a build server somewhere in network proximity wouldn't be awful, unless there are real security requirements that prevent that happening.
Dave
In reply to Re: Perl Module Installation
by davido
in thread Perl Module Installation
by misteradey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |