Geoffrey Young wrote: > >> >> and 2.0 doesn't have perl sections yet :( >> >>> any thoughts on using the blib pragma over the various use lib stuff >>> in modperl_inc.pl? >> >> >> >> I think we need to rethink the whole concept of how Apache::Test and >> its elements manipulate @INC. What are the demands from you Geoff, as >> its user? > > > > ok, the only thing I've seen that Apache::Test doesn't handle gracefully > in 1.3-land is the blib thing - I have lots of modules that use XS > (either by choice or via the directive handler API) and they all need > extra tweaking in order to run. > > the problem is that the typical 1.3 way to handle this doesn't work - I > can't rely on startup.pl to set @INC because it comes after > extra.conf.in is loaded. > > personally, I think the right way to handle this is to require no > tweaking by the end-user at all - if I can > > # make install > > and then > > PerlModule My::Module > > works using a standard mod_perl build, then Apache::Test should work > with only the PerlModule directive as well.
Yes, yes, I'm getting burned on the exact problem with 2.0 and modules in sub-dirs (which are like external modules, if I build from inside them). > it seems to be that this is exactly what the blib pragma is for, but I > haven't tried taking out the stuff that Apache::Test writes in and only > using blib. > > (I know, patches welcome, etc :) Once Doug commits the new Apache2 magic, I'll try to resolve this problem. But I still need to know what should we do about @INC mungling, and Include ordering, because that's where the problem comes from. __________________________________________________________________ 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]
