if you're seeing something different but following the same steps, then we clearly need some tests to flesh this out, though I'm not sure now how we would undo -T for a single set of tests in the suite.
Sorry, you are right, I was looking at the wrong printout. I did:
use Data::Dumper;
warn Dumper [EMAIL PROTECTED];
warn Dumper $ENV{PERL5LIB};So @INC didn't have it, but $ENV{PERL5LIB} had.
So it's only when PERL5LIB is set outside and PerlPassEnv is used it affects mod_perl. Though since everybody is better off running with -T, it doesn't make any difference. The question is whether we should support PERL5LIB despite -T or not.
>>> I don't see that in core. I see some special handling for tainting >>> in the test suite, though. but you could be right. >> >> which core? 1 or 2?
In mp1 tt does that regardless tainting:
in src/modules/perl/mod_perl.c:
/* SetEnv PERL5LIB */
if (!MP_INCPUSH(cld)) {
char *path = (char *)table_get(r->subprocess_env, "PERL5LIB"); if (path) {
perl_inc_unshift(path);
MP_INCPUSH_on(cld);
}
}notice that it doesn't even split path on ':'.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
