On Jul 28, 2005, at 6:26 PM, Randy W. Sims wrote:
Neither CPAN.pm nor CPANPLUS do a scan of cpan.org, correct? They get
info from the package list. So, only the indexer needs to be made
smart - don't catalog perl6 modules in the old package list. CPAN.pm &
CPANPLUS will happily ignore anything else.
That's true. All the smarts could be centralized in the indexer.
But then there's the problem of making sure when someone's browsing
CPAN manually (on a regular mirror or on search.cpan.org or wherever)
that they don't accidentally download perl6 modules when they meant to
download perl5 modules. CPAN(PLUS)? may use only the index files, but
people's brains don't.
As far as distinguishing, there a lot of talk in the past in the
context of Apache2 about adding a field ("generation") which serves
basically the same purpose - It distinguishes between multiple code
bases intended for different targets.
Personally I really don't like the idea of the "generation" field. I
think it's too strict a mechanism for a nebulous notion.
-Ken
