On the second thought, chances are that nobody has been using a multiple-paths PERL5LIB, otherwise they would have complained like you did. So if nobody objects and we agree that the current behavior is buggy, +1 for your patch.
So what do you think, fix it? or document it?
and of course need to fix that in mp2.
+1 on fixing it to behave properly in mp1.
I'll tacked the mp2 bits this week.
Should we try to squeeze it into 1.29? If so do we need another release candidate? Since we need 1.29 out asap, because of the bug in 5.8.1, I suggest that we release 1.29 as it is now. Then hopefully we will release 1.30 some time soon (including the PERL5LIB fix). I know there are quite a few patches that Philippe has planned to put in and we want them to sit in the cvs for some time to get people time to test it out well.
__________________________________________________________________ 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]
