in reply to (tye)Re2: The Missing Win32::Perms Module
in thread The Missing Win32::Perms Module

Because 99% of Windows Perl users don't have C compilers and CPAN is built around using your C compiler to install stuff.

Ok, this is true, but all you need to work with CPAN is a functional 'make' and 'install', correct? Does CPAN depend in on the C preprocessor or somesuch? There are win32 ports of GNU make, and install shouldn't be too tough...just seems silly not to support CPAN. Maybe licensing issues were a problem (GPL, whatever), but they could easily have rolled their own instead of writing ppm...heck, I've written my own dependancy graph traversal system.

Heh, this is something of a pet peeve for me, seeing as I've been shackled to a perl on Win32 project for a month or so now. Well, that and the complete insanity that is the Win32::PerfLib structures. Trust me, stay far, far away, monks. =)

Trinary

  • Comment on Re: (tye)Re2: The Missing Win32::Perms Module

Replies are listed 'Best First'.
(tye)Re3: The Missing Win32::Perms Module
by tye (Sage) on Dec 30, 2000 at 02:42 UTC

    Many modules only need "make". Many modules include C code and need a C compiler. Perhaps it would be a good thing if ActiveState would refrain from making PPM distributions for modules that don't require a C compiler. Perhaps it would be even better if the PPM client knew how to use CPAN for such modules instead.

    I think it would be great if ActiveState would switch to building their free binary distribution of Perl with a free C compiler so only the lazy would have to use PPM. (:

    P.S. Win32::PerfLib probably just returns the insanity that is Win32 performance data blocks. Those are certainly lots of fun!

            - tye (but my friends call me "Tye")
[reply]

In Section Meditations