Can anyone explain a safe and reliable way of making the functionality of the SSL.pm available to my script directly, considering that this module would be called from a properly installed module? I understand that, theoretically, I am able to roll the code of virtually any .pm into my own scripts and have them work, but I suspect (maybe wrongly) that in order to get SSL functionality, I would probably also have to include all of its parent packages (which would be pretty dumb, I think).
Am I stuck here or is there a monkishly clever way out of this tight little box?
Yukio
In reply to Pseudo-installing modules by Yukio
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |