After a good night sleep Config_heavy.pl isn't quite so scary. A s!.:/strawberry!$strawberryDir!g does most of the work, but there are these other options that probably shouldn't be left as they are because they still contain unix paths. This might account for the occasional X:\strawberry\perl\lib/foo/baa mangled paths seen in logs and error reports.

glibpth='/usr/shlib  /lib/pa1.1 /usr/lib/large /lib /usr/lib /usr/lib/
+386 /lib/386 /lib/large /usr/lib/small /lib/small /usr/ccs/lib /usr/u
+cblib /usr/shlib '
...
locincpth='/usr/local/include /opt/local/include /usr/gnu/include /opt
+/gnu/include /usr/GNU/include /opt/GNU/include'
loclibpth='/usr/local/lib /opt/local/lib /usr/gnu/lib /opt/gnu/lib /us
+r/GNU/lib /opt/GNU/lib'
...
strings='/usr/include/string.h'
...
sysman='/usr/man/man1'
...
timeincl='/usr/include/sys/time.h '
...
xlibpth='/usr/lib/386 /lib/386'
[download]

Update: Read Config manual page. Some of these are redundant. Others are easily redirected, and should really have been sorted during compile time, i.e. the Configure script didn't really set them correctly prior to compiling. It seems safe to redirect them to appropriate include and lib directories.

I discovered exactly the same thing, nowhere nearly as scary as it first appeared.

So I've implemented the auto-detecting version of Config_heavy.pl as well, and added it to the repository.

I've noticed the unix paths as well, but I'm unsure what the hell the implications of that are...

Should I go through the makefile before I compile Perl and strip all those out? I dunno yet...