Re^2: Five Features Perl 5 Needs Now

Easier said then done. There's CPANPLUS and it took a lot of effort to get that integrated in the core. On the author side, there is Module::Build and a few other alternatives to Extutils.

That wasn't his point. He was suggesting that the build/test/install cycle is kludgy. Which is one reason why there is PPM. Of course, someone has to build and maintain PPM files and the latest and greatest releases aren't always available. Which is why some people still want to build/test/install direct from CPAN. (c.f. Strawberry Perl.)

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Comment on Re^2: Five Features Perl 5 Needs Now

Replies are listed 'Best First'.

Re^3: Five Features Perl 5 Needs Now
by Jenda (Abbot) on Dec 21, 2008 at 23:21 UTC

The reason for PPM is that most Windows installations lack a C compiler plus the compiler that's used for the most spread Windows distribution of perl is not free.

Jenda
Support Denmark!
Defend the free world!

[reply]

Re^4: Five Features Perl 5 Needs Now

by xdg (Monsignor) on Dec 22, 2008 at 01:25 UTC

the compiler that's used for the most spread Windows distribution of perl is not free

That's not quite true. The express edition is free (as in beer, at least) and works fine with ActiveState. (It just doesn't come automatically installed and configured like in Strawberry.)

And just because PPM is useful on Windows doesn't mean it can't be used elsewhere to avoid build/test/install. I'm not saying one should, but I'm clarifying chromatic's point that the standard CPAN build/test/install cycle is kludgy and PPM is one example of an alternative.

-xdg

[reply]