By gst
via journal.naveeng.com
Submitted: Oct 17 2007 / 04:11
How many times PERL developers have to scratch their heads when they find that there is a module dependency which is breaking their code. Worse, they do not have sufficient privileges to install the required modules on the system. And the worst - there is no immediate way to get the module installed and the application needs to be tested/deployed ASAP! Well, I faced a similar situation during my experience in deploying a website on a shared hosting account, where I was on the mercy of the Hosting Service Provider to decide which modules I’m going to use and which not. But this is hardly the way a programmer works, and more so for a PERL programmer! I came across a few wonderful workarounds (hacks!) to overcome the above.
Add your comment