On Mon, 22 Jan 2007 09:28:56 +1100, "Sisyphus" <[EMAIL PROTECTED]> wrote:
>On build 817 and earlier, @INC lists perl/lib before perl/site/lib. (This is >in keeping with other versions of Win32 perl.) >But with build 819, @INC lists perl/site/lib ahead of perl/lib. > >Seems an odd change to make. Anyone know why that change was made ? The change was made to make it easier to update bundled modules, especially with PPM4. All bundled modules are now installed in the perl/lib tree and a clean install should result in an empty site/lib tree (except for the sitecustomize.pl file). PPM4 internally will load modules from the lib tree first, so it will be possible to update even LWP or HTTP-Parser etc because the newer versions will be installed into site/lib. With older versions of ActivePerl installing updated versions of core modules would have no effect because the new versions would always be shadowed by the version already in perl/lib. This also means that it should be even easier to keep your own Perl/site/lib tree around because it only contains code that you installed yourself. However, this also means that you should not install ActivePerl 818 or later on top of 817 or earlier because then you will end up with older bundled modules in the site/lib tree that now prevent the newer versions from loading. At least the Windows installers for 820 will detect this situation and refuse to install on top of 817 or earlier. Note that the ActiveState PPM repositories don't yet include updated versions of bundled modules, but we are working on this. They will only be visible via PPM4 though. Cheers, -Jan _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
