On Wed, 16 Nov 2005, Reini Urban wrote: > Jan Dubois schrieb: > > Even if you compile and install libwin32 itself, the Win32 module > > will not be used by Perl because it gets installed in the site/lib > > directory, which is being shadowed by the core Perl version of the > > Win32 module. All the other libwin32 modules will be updated though. > > > > (Just for reference, this is different for cygwin Perl, which does > > not yet come with a core version of Win32 installed in the lib tree. > > But this is going to change in the future.) > > Did I miss something in p5p? Currently we have Win32 in vendor_perl. > The CORE counterpart is named Win32CORE and is in archlib. Why do we > want the CORE part of Win32 being renamed to Win32?
It is not the Win32CORE part, it is the Win32 part that is in the core Perl for $^O eq "MSWin32" and part of libwin32 for $^O eq "cygwin". You'll find Win32 in the core distribution under win32/ext/Win32. But the Win32CORE part should be unified between both branches too, to make sure the code stays in sync. I'm referring to this thread on p5p: http://aspn.activestate.com/ASPN/Mail/Message/perl5-porters/2887170 Once cygwin builds Win32.pm/Win32.xs from the core Perl distribution too I would spin off Win32 into a separate CPAN release for legacy Perl versions only. Cheers, -Jan
