Mark Stosberg wrote: [...]
[...]Is there a simpler way to make Apache::Reload work when there are relative 'use lib' paths in the code?
Thank you very much for your prompt and helpful to reply.
You're welcome, Mark ;)
Just to add a bit more to this thread:
I did follow this advice about setting up @INC at server startup time. However, that didn't seem to change my results. What did seem to help was relying on these declarations exclusively-- I removed my relative 'use lib' calls in the code and had less problems.
I haven't seen such a behavior before. I'll need a reproducable test case if you want me to look at it. In case you would like to submit one, Geoff has kindly prepared a skeleton perfectly suitable for this purpose:
http://perl.apache.org/~geoff/bug-reporting-skeleton-mp1.tar.gz
also linked from:
http://perl.apache.org/docs/1.0/guide/help.html#How_to_Report_Problems
__________________________________________________________________ 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
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
