in reply to Re: [Inconsequential] Strawberry Perl and MM_Win32.pm
in thread [Inconsequential] Strawberry Perl and MM_Win32.pm

Better suggestions welcome

No, I don't have a better suggestion - though I would do it differently.

Normally, when one updates a core module on Win32, it goes into perl/lib, clobbering the old version in the process. I personally don't see any reason to change that behaviour.

Looking a little more closely at the Strawberry distro, we see there are still some MakeMaker modules in perl/lib/ExtUtils - eg EU::Liblist, which is duplicated in perl/site/lib/ExtUtils. (I think the duplicated modules are identical. One hopes so, as its the ones in perl/lib/ExtUtils that will be loaded.) If EU::MM is going into perl/site/lib then I think it would be a good idea to remove *all* of the MakeMaker modules from perl/lib/ExtUtils.

Anyway .... nothing to lose any sleep over. I was merely taken aback for a few minutes when I went to open MM_Win32.pm and it wasn't there !! :-)

Cheers,
Rob
  • Comment on Re^2: [Inconsequential] Strawberry Perl and MM_Win32.pm

Replies are listed 'Best First'.
Re^3: [Inconsequential] Strawberry Perl and MM_Win32.pm
by xdg (Monsignor) on Jan 21, 2007 at 13:31 UTC
    I was merely taken aback for a few minutes when I went to open MM_Win32.pm and it wasn't there
    perldoc -m ExtUtils::MM_Win32

    This (along with "-l") is a handy feature of perldoc. I have $ENV{PAGER} set to "less.exe" and $ENV{EDITOR} set to "gvim.exe" so after the command above, I just type "v" and it pops me into the editor with the right file. It saves having to navigate directories.

    -xdg

    Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.