Re^4: [Inconsequential] Strawberry Perl and MM

Also in the docs, "Upgrading from ActivePerl 5.8.x", point 2 says:

Manually delete all directories beneath the Perl installation directory (by default C:\Perl) except the site\lib directory.

I've been doing this for a few years now. Does your quote imply that what used to be installed in the site dir is now in the "perl install area" and that I could now have the same modules installed in both? @INC lists the site dir first so am I right in thinking a possibly more recent version of a module in the "perl install area" won't be picked up?

If this is so what is the best way of fixing this?

Comment on Re^4: [Inconsequential] Strawberry Perl and MM_Win32.pm Download Code

Replies are listed 'Best First'.
Re^5: [Inconsequential] Strawberry Perl and MM_Win32.pm by CountZero (Bishop) on Jan 21, 2007 at 14:34 UTC
Personally I think it is not a good idea to follow this upgrade advice and I have made a new clean install and added the modules I needed so they appeared in the `perl/site/lib` directory. Indeed modules in `perl/site/lib` will mask modules in `perl/lib`. Given the chance that some modules in my (old) `perl/site/lib` were less recent than in the (new) `perl/lib` I did not take any risks here. CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply] [d/l] [select]
Re^5: [Inconsequential] Strawberry Perl and MM_Win32.pm by syphilis (Archbishop) on Jan 22, 2007 at 23:10 UTC
Manually delete all directories beneath the Perl installation directory (by default C:\Perl) except the site\lib directory. I don't see any problem with that upgrade advice unless you're updating from build 817 (or earlier) to build 818 (or later) - in which case you should first remove the existing version entirely. Cheers, Rob	[reply]