|Subject:||Installation info goes to ARCH dir even for Pure Perl installs|
Versions: As supplied in perl-5.8.5, so ExtUtils::MakeMaker 6.17 ExtUtils::Install 1.32 ##### The Makefile produce by ExtUtils::MakeMaker on Unix installs the .packlist and perllocal.pod information in architecture-specific locations even when the module is Pure Perl and hence is installed in an architecture-independent locations. e.g., the pure_perl_install install node starts: pure_perl_install :: $(NOECHO) $(MOD_INSTALL) \ read $(PERL_ARCHLIB)/auto/$(FULLEXT)/.packlist \ write $(DESTINSTALLARCHLIB)/auto/$(FULLEXT)/.packlist \ $(INST_LIB) $(DESTINSTALLPRIVLIB) \ $(INST_ARCHLIB) $(DESTINSTALLARCHLIB) \ ..... The result is that for installations which share the Pure Perl locations across architectures this information is missing from the "other" installations. Hence modules such as Extutils::Installed produce incomplete information. It should be possible for .packlist and perllocal.pod to be installed/edited under DESTINSTALLPRIVLIB (DESTINSTALLSITELIB and DESTINSTALLVENDORLIB) for Pure Perl modules. Also, the perllocal.pod, although it is currently put into DESTINSTALLARCHLIB, is written to say that the module has been installed into INSTALLPRIVLIB (i.e. compiled modules are reported as being in the Pure Perl location).