I am guessing that the intent of your message is that CPAN will not work
with a normal windows configuration?
I run CPAN. My configuration...
-MSC version 5.0
-I built Perl from the CPAN source (not a AS build)
-I use 4NT as my shell, which perhaps does more than the regular Win command
shell but it certainly isn't a unix shell.
-I have some unix clone tools in my path.
I suspect that it is only the last part of the above the determines whether
CPAN works or not (these same tools can be acquired at
http://www.itribe.net/virtunix/). I can't really see that it matters that
the build is AS or not.
> Behalf Of Soren Andersen
>
> ...
>
> Rest of the points skipped because the major issues are the ones at top,
> until they get solved the rest are moot. CPAN.pm as currently set up is
> heavily oriented towards UNI* , it's a major porting job. i'd love to see
> it happen.
>
> soren andersen
> -- Who DOES have CPAN on his AS ActivePerl 522 -- at cost of
> several hours
> over several days of hacking Config.pm, etc.
>
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
