Why aren't CPAN modules a viable option? Is this because they are forbidden by policy or because you do not have control over the perl installation tree?
In the latter case, at least, you could install CPAN modules in a lib directory distributed with your application. FindBin and use lib are your friends after that (see FindBin for examples).
Matt
| [reply]
[d/l] |
While policy does not explicitly forbid CPAN modules, they are completely unsupported inhouse. Without inhouse support there's too many hurdles to overcome to use CPAN modules effectively. It's more like enforcing a ban by attrition than an outright ban.
I'm working on 'em though projects like the one I'm working on currently will go a long way to insinuate Perl a little deeper into the corporate culture/infra-structure
For now that has to be the best next step. Once they are
comfortable with that then progress on CPAN can be made. I know that might sound a bit backword to outsiders but I've been advocating actively for a few years here. Patience and solid code in the clutch is the best course for now :)
coreolyn
| [reply] |
