Re: Perl versions conflict help

So, first question is why ActiveState is not able to find its own config.pm?

Because by setting PERL5LIB variable you're explicitly asking it to start search libraries in specified directory. -I switch doesn't prevent from using PERL5LIB, though directory specified with -I is used first.

Comment on Re: Perl versions conflict help Select or Download Code

Replies are listed 'Best First'.
Re^2: Perl versions conflict help by jujiro_eb (Sexton) on Nov 13, 2009 at 23:28 UTC
Hi Zwon, I totally get what you are saying. However, ELISHEVA writes in one of her threads with me, "Keeping every thing separate also saves you from a nightmare of version compatibility issues. You don't have to worry about your application breaking if other applications need older or newer versions of a module". To me, unsetting PERL5LIB is breaking someone else's application. I suppose there is no way around it. Ash	[reply]
Re^3: Perl versions conflict help by zwon (Abbot) on Nov 14, 2009 at 10:20 UTC
In this case you can set `PERL5LIB` on a per application basis.	[reply] [d/l]
Re^4: Perl versions conflict help by Anonymous Monk on Nov 14, 2009 at 10:27 UTC
`$ cat myfrobnicator6.pl #!/super/super/frobnicator/bin/perl -- use lib '/super/super/frobnicator6/lib'; MyFrobnicator6->run; exit;` [download] for windows, use pl2bat, modify to call `C:/suuper/super/frobnicator/bin/perl.exe` or use PAR/pp	[reply] [d/l] [select]