>Didn't go for that option, because I am running the scripts from
>crontab. So environment vars may not work ( actually havent tried that,
>but I m kinda sure they wont!)
>
Just try,
0 * * * * (export PERL5LIB=/your/lib/path; perl xxx.pl)
The perl script must be run on the same shell of the ex
>
>Thanks for the people who responded to original query.
>Another related query.
>Whats the best way to specify common set of include library directories,
>so that I don't end up including (use lib OR "-I") in each file using my
>local modules. (recursive include!)
>
Then how about modifying @IN
On 22 Mar 2007 at 8:59, Kumar, Akshay wrote:
> Thanks for the people who responded to original query.
> Another related query.
> Whats the best way to specify common set of include library directories,
> so that I don't end up including (use lib OR "-I") in each file using my
> local modules. (rec
Thanks for the people who responded to original query.
Another related query.
Whats the best way to specify common set of include library directories,
so that I don't end up including (use lib OR "-I") in each file using my
local modules. (recursive include!)
>
>I am playing around with a set of perl scripts. Need to figure out
>following things.
>A) move out common code from the set of scripts and have them include
>that common code. (something equivalent of #include!) . Most of the
>common code is about some arguments (proxy-url, database, user, pass
>
