On 10/19/2012 09:48 AM, Shlomi Fish wrote: > I keep receiving such erroneous reports from Windows machines, and > apparently they are caused by overloaded PERL5LIB variables. > > Would it be possible to simply load the @INC from a file containing > each path per line and populate it in a loop in Perl inside a BEGIN > {...} block to eliminate such erroneous warnings?
Sure, I see no reason not to work. There is even a special 'hook' in the form of sitecustomize.pl being read at startup, when such a support has been compiled into perl ($Config{usesitecustomize}). However, I don't know which Perl builds enable this feature; perlbrew doesn't enable this feature by default, neither does Ubuntu. I remember seeing such an approach a few times in hosting environments, to add to @INC libraries of Cpanel-installed software. Przemek