Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • From what I understood, this is among the many things that CPAN6 [] was supposed to solve. I looked at the presentation and could not understand it at first, but maybe I will now. As I recall I had read the Aegis version control page with its features-list when I was looking for a VCS and not understanding what most of its features mean, and then after I had used BitKeeper, understanding most of them, so I guess maturity and experience count. :-).

    But like I want to say, the current CPAN ownership, release and versioning system leaves a lot to be desired. It seems like a lot of patchwork to me with hacks upon hacks. I still don't understand why there can only be one namespace master in PAUSE, and not several who can hand out uploading bits. And naturally there should be a way in the admin screen to assign ownership to all modules maintained by the Catalyst team to any of the Catalyst maintainers. And naturally, people would sometimes love to create alternative CPAN branches of modules that were forgotten or unmaintained without their missing-in-action author's approval, or as a github-like fork of the module that will hopefully be merged into the main one.

    CPAN is probably better than most of the source code repositories for other languages that I know about. Even its comprehensiveness is second to none. But in its years it has accumulated a lot of historical cruft, partly due to "Release Early, Release Often". So I think something like CPAN6 will be a good thing, assuming we can get everyone to gradually switch to it without breaking production (possibly by syndicating stuff to the old CPAN and its mirrors.).