Cut'n'paste the code from Parallel::ForkManager into a module that you "wrote". It's PurePerl. Heck, if you need it, I cut'n'pasted the code into this node (within the readmore). If you feel bad, add an attribution.
Note: a restrictive development environment is one that encourages the development of costly and buggy software. You have a perfectly good solution that was developed under the same development model that Perl itself was developed under. Is that seriously a big issue?
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
| [reply]
[d/l] |
Even in a restrictive environment you can put your own module-directory and install the module there. With simple pure perl modules (no compiler needed) you can simply fetch the module file(s)? and copy it to that directory.
Parallel-ForkManager is pure perl, so no problem. You only have to tell perl where to look:
use lib qw(/some/lib/path);
And even in the most restrictive environment you can simply put the modules code in your scriptfile.
modules with c-code are more complicated. you´re lost when you don´t have access to a compiler, unless you find it prebuilt.
if you have no shell access, these nodes might be helpful:
Install Perl Modules Using FTP Without Having Shell Access?, Installing modules without root and shell
| [reply]
[d/l] |