On 05/09/00, "Ned Konz <[EMAIL PROTECTED]>" wrote:
> Joe Schell wrote:
> 
> > First, the CPAN module relies on a number of tools that wouldn't be
> > available for most common installs of windows.
> 
> AFAIK, CPAN only expects to have a make utility available. That's
> something that could be fixed in a README (point 'em to Microsoft's NMAKE15.EXE or 
>something).

You are not correct on this one Ned. CPAN.pm requires more than Make. It 
wants to find (as a user will discover if they ever get so far as to run 
the initial config setup) at least (from memory): a tar [i think], a 
FTP-something [well known to UNI* users, I had to search the Net -- 
successfully -- to find one that had been ported to Win32) etc .. It is a 
seriously considerable list of tools that are no way going to be on a 
typical Win user's system. And differing licensing issues for some of those 
tools might very well preclude any notion of "bundling" them into some 
special download archive for PPM.
 
> And there has to be some way to get the sources. However, doesn't the AS
> distribution come with the LWP stuff?

> > Second, it is my impression that ppm installs 'built' modules.

That's right, only in the sense that anything using XS subs must have its 
dependencies that contain those subs [libs] _compiled_ and linked-in -- 
otherwise there's no meaning to talking about "built" or "not built" in 
plain Perl modules -- its all ascii human-readable source if its Perl; it's 
just a question of placing the module souce file *.pm in the right 
directory.

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]

Reply via email to