It's been something of a long-standing (second-order) problem that packages are just tarballs (or bzipball, or zips, etc).
The lack of a "standard" file extension means that we can't sanely implement features like "double-click to install" on operating systems and browsers with file extension association capability. If we are looking at not only sharing user permissions between the two languages, but also sharing the author directories directly, this would seem like a highly opportune moment to switch to a new specific extension for P6 distributions. It would help the current indexer, because Andreas can just ignore files with that extension, and it would make it trivial for the new indexer to ignore Perl 5 and legacy files. Adam K On Mon, Jan 4, 2010 at 10:23 PM, Zefram <zef...@fysh.org> wrote: > Ovid wrote: > >From the Rakudo test suite: >> >> use perl5:Text::Wrap 'wrap'; > > That would seem to settle it, then: perl5:Config::INI does not conflict > with perl6:Config::INI. The absolutely next thing we need is naming > convention for Perl 6 module distributions on CPAN: it could perhaps > be p6-Config-INI-1.00.tar.gz, or Config-INI-1.00.tar.gz in a different > directory from where the Perl 5 one lives. The next thing we need after > that is an index of Perl 6 modules on CPAN. > > -zefram >