The problem we're having is this. When a standalone Apache-Test is built and installed its files get installed into INSTALLSITELIB (since it has no arch to install, all pure perl). For example lib/site_perl/5.8.3/Apache/TestRun.pm. When Apache-Test is installed via modperl-2.0's make install Apache-Test files end up in INSTALLARCHLIB (since modperl-2.0's own files have arch modules). For example the same file now gets installed at: lib/site_perl/5.8.3/i686-linux-thread-multi/Apache/TestRun.pm
Now unless a user uses 'make install UNINST=1', we end up with two versions of Apache-Test installed. If the user updates her version of Apache-Test (which will go into INSTALLSITELIB), it won't take any effect since INSTALLARCHLIB comes before INSTALLSITELIB in @INC. Which is a bad thing.
So a few questions/suggestions:
1) Shouldn't MM at least warn if a copy is found elsewhere in INSTALL targets, besides the target it installs to?
2) I see that MM doesn't have any logic to decide which files go where once they are in blib. On 'make install' it just grabs blib and if at least one file goes into INSTALLARCHLIB all of them go there. I think in this case the pure_site_install target is the one that gets to run.
Is there a way to tell that files from a sub-dir should go to INSTALLSITELIB and not where the rest of the files go to? I couldn't find a way to do that. It's probably going very tricky to do.
Pushing UNINST=1 for the user is probably an unwise thing to do.
Thanks.
__________________________________________________________________ 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
