Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

CPAN::Index 0.01: From CPAN to JSAN and back again 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • the entire code ecosystem that sits above the Perl 5 language surface and just happens to include "CPAN"

    We need a name for this. Would CPAN Ecosystem do?

    • CPAN Ecosystem probably doesn't cover it accurately enough. Perl 5 Ecosystem might cover it more accurately, but it's really Larry's call. I don't even know if he has a term for it.

      I've generally found the surface concept to work well, even up to conversations with Audrey and Larry.

      The problem with naming is that it would need to include things like the Perl core, or rather the non-essential modules like File::Spec that are dual-lifed.

      It includes Bundles, and the CPAN client itself, and Inline, and a hundred other bits and pieces that are distinct works in their own right, and not necesarily part of the CPAN, but which form distinct elements of the richness.

      But I think there is qute possibly a need for a distinction between The CPAN that people like aevil talk about (just the FTP and mirrors and such) and what the layman perceives as CPAN, which includes rt.cpan and search.cpan and the dozen other services.

      Perhaps "CPAN Cloud" or some such? :/
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.