Mike Blazer wrote:
> 
> > It might be helpful to people if someone who has used a non-M$C/C++ cc
> > posted / made available their Config.pm so that those who wish to emulate...
> 
> No need. It will not help, to my mind it's quite wrong to edit Config.pm massively - 
>it should be created when you (or your vendor) are compiling your Perl. And this 
>compilation also creates lib\CORE\perl.lib that is compartible only with the compiler 
>that built Perl. So, whatever you put to Config.pm will not work.

I think we may be talking about two different config.pm files:

        there's the Perl Config.pm (which, IMHO shouldn't be edited)

        and there's the CPAN/Config.pm, which has its settings for tools, etc.
(this can be edited fairly safely).

Or maybe I'm just getting the wrong impression.

There is support in ExtUtils for NT without external utils -- cp, mv,
rm, etc. are all
provided for. CPAN itself doesn't use any external utils other than:

  'ftp' => q[/usr/bin/ftp],             optional
  'gzip' => q[/bin/gzip],               will use Compress::Zlib
  'lynx' => q[/usr/bin/lynx],           optional
  'make' => q[/usr/bin/make],           needed (but could use Perl make/dmake?)
  'ncftpget' => q[/usr/bin/ncftpget],   optional
  'pager' => q[/usr/bin/less],          can use MORE.EXE if necessary
  'shell' => q[/bin/bash],              only used for "look" command; could be CMD
  'tar' => q[/bin/tar],                 could use the TAR replacement in Archive::Tar
  'unzip' => q[/usr/bin/unzip],         only needed if .zip files distributed

The only other external utils that could be needed are the ones used by
Makefile.PL,
which (if it uses MakeMaker) will use the Perl equivalents if the
external commands
aren't available.

That only leaves compilation, which isn't necessary for the majority of
Perl modules.

-- 
Ned Konz
currently: Stanwood, WA
email:     [EMAIL PROTECTED]
homepage:  http://www.bike-nomad.com

---
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]

Reply via email to