Yes, but as I neglected to mention initially, at least one of the scripts in question will be a widely distributed script under the control of sysadmins with their own concerns. It has to be system only perl or a reinvented wheel.
I will probably check the YAML and Config:: modules to see if any are already used by the projects my other script is geared toward, but I do need the most secure system only method I can get hold of.
| [reply] |
| [reply] |
Agreed. Problem is I personally have no access whatsoever to the environment the script is expected to run in. The Perl installation is homogenous over a network of hundreds of machines, so getting it upgraded or modified is a serious undertaking - not that it isn't automated in some way, just that changing something on so many systems is not done lightly - nor should it be.
If I want something included as a dependency of the project, I pretty much have to include it as part of the project. I probably have the option of simply including the .pf file in the CVS package, but then I have a lot of questions to answer concerning duplication, security of the module, etc.
This is starting to get interesting :)
| [reply] |